Bitget audit reports

Base, Ethereum, Solanabitget.comX

Bitget has 18 public audit reports from BlockSec; the latest is BlockSec, 30 Oct 2026; no critical findings reported.

Critical findings
No open critical findings
Across 18 reports.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm15

Statuses are the security firms’ own

15 findings are still open or acknowledged in the firms’ reports: 1 medium, 14 low (all open).

Medium
1
Low
14
  • Medium Open

    Lack of access control in the function handleFeeWithSign()

    Bitget · BlockSec · 30 Sep 2025 · Report ↗

  • Low Open

    Lack of proof of possession in function setAccountKey()

    bitgetwallet · BlockSec · 30 Oct 2026 · Report ↗

  • Low Open

    Stale validator configuration after emergency deactivation

    bitgetwallet · BlockSec · 30 Oct 2026 · Report ↗

  • Low Open

    Lack of allowance revocation after swaps

    Bitget · BlockSec · 17 Jul 2026 · Report ↗

  • Low Open

    Lack of rebaseIndex binding in signed authorizations

    Bitget · BlockSec · 9 Jul 2026 · Report ↗

  • Low Open

    Inconsistent timelock enforcement for selector risk level changes

    bitgetwallet · BlockSec · 3 Jun 2026 · Report ↗

  • Low Open

    Lack of delay restriction on function cancelOperation()

    bitgetwallet · BlockSec · 3 Jun 2026 · Report ↗

  • Low Open

    Unrestricted partner fee recipient and partner fee allocation in partner fee-sharing swap flows

    bitgetwallet · BlockSec · 18 May 2026 · Report ↗

  • Low Open

    Incorrect rounding direction in rebase index updates

    Bitget · BlockSec · 15 Apr 2026 · Report ↗

  • Low Open

    Incorrect staleness validation for Pyth price feeds

    Bitget · BlockSec · 15 Apr 2026 · Report ↗

All 15 open and acknowledged findings

Audits18

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
bitgetwalletSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 3 low
1 fixed · 2 open
GitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: None listedGitHub ↗
BitgetWalletSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: None listedGitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: None listedGitHub ↗
bitgetwalletSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: None listedGitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 1 low
1 open
GitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: None listedGitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 1 low
1 open
GitHub ↗
bitgetwalletSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 4 low
2 fixed · 2 open
GitHub ↗
bitgetwalletSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 1 low
1 open
GitHub ↗
bitgetwalletSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 1 low
1 fixed
GitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 1 low
1 fixed
GitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 4 low
2 fixed · 2 open
GitHub ↗
Bitget WalletSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 2 low
2 open
GitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 2 high · 1 medium · 3 low
4 fixed · 2 open
GitHub ↗
bitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 1 high · 2 low
2 fixed · 1 open
GitHub ↗
blcokchainbgSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: 1 low
1 open
GitHub ↗
BitgetSecurity firm: BlockSecDate: Scope: Not recorded; see the reportNone openFindings: None listedGitHub ↗

Findings28

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High003
Medium100
Low14010
MediumLack of access control in the function handleFeeWithSign()Bitget · BlockSec · 30 Sep 2025Open

The report gives no description here.

Open the report
LowLack of proof of possession in function setAccountKey()bitgetwallet · BlockSec · 30 Oct 2026Open

The report gives no description here.

Open the report
LowStale validator configuration after emergency deactivationbitgetwallet · BlockSec · 30 Oct 2026Open

The report gives no description here.

Open the report
LowLack of allowance revocation after swapsBitget · BlockSec · 17 Jul 2026Open

The report gives no description here.

Open the report
LowLack of rebaseIndex binding in signed authorizationsBitget · BlockSec · 9 Jul 2026Open

The report gives no description here.

Open the report
LowInconsistent timelock enforcement for selector risk level changesbitgetwallet · BlockSec · 3 Jun 2026Open

The report gives no description here.

Open the report
LowLack of delay restriction on function cancelOperation()bitgetwallet · BlockSec · 3 Jun 2026Open

The report gives no description here.

Open the report
LowUnrestricted partner fee recipient and partner fee allocation in partner fee-sharing swap flowsbitgetwallet · BlockSec · 18 May 2026Open

The report gives no description here.

Open the report
LowIncorrect rounding direction in rebase index updatesBitget · BlockSec · 15 Apr 2026Open

The report gives no description here.

Open the report
LowIncorrect staleness validation for Pyth price feedsBitget · BlockSec · 15 Apr 2026Open

The report gives no description here.

Open the report
Show 5 more
LowIncorrect update in the function handle_action_token_out()Bitget Wallet · BlockSec · 21 Nov 2025Open

The report gives no description here.

Open the report
LowLack of handling pumpfun sell operation in swap_v3() functionBitget Wallet · BlockSec · 21 Nov 2025Open

The report gives no description here.

Open the report
LowPotential DoS due to precision loss on feeAmountBitget · BlockSec · 30 Sep 2025Open

The report gives no description here.

Open the report
LowLack of updating rewardAmount in function unStakeAndClaim()bitget · BlockSec · 25 Sep 2025Open

The report gives no description here.

Open the report
LowLack of nonce check during swapblcokchainbg · BlockSec · 23 Sep 2025Open

The report gives no description here.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

Bitget: questions

Is Bitget audited?

Trustblock holds 18 public audit reports for Bitget, dated 27 Jun 2025 to 30 Oct 2026. The latest is by BlockSec (“bitgetwallet”).

Who audited Bitget?

BlockSec wrote the 18 reports Trustblock holds for Bitget.

Are there open findings in Bitget’s audits?

15 findings are still open or acknowledged in the firms’ reports: 1 medium, 14 low (all open). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="bitget"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us