GMX Updates 2

Guardian Audits14 Jun 2024Code version: not recorded (see the report)

Audit · firm’s term: security review

Part of Guardian Audits’ series

Guardian Audits reviewed GMX (GMX Updates 2) on 14 Jun 2024: 18 findings, 2 critical; 10 marked fixed, 8 acknowledged.

2 critical findings, fixed

Open the report Open GMX’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings18

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	2
High	0	0	1
Medium	0	3	4
Low	0	5	3

CriticalLimitSwaps Cannot Execute After Request ExpirationFixed

The report gives no description here.

CriticalLiquidations Prevented With updateOrderFixed

The report gives no description here.

HighKeeper's Not Remunerated For Cancellation CallbackFixed

The report gives no description here.

MediumCallback Gas Validation Ignores 63/64 RuleFixed

The report gives no description here.

MediumNo way for user to add cancellation receiverFixed

The report gives no description here.

MediumOld Estimated Execution Base Gas Fee UsedFixed

The report gives no description here.

MediumOrders Which Close Positions May Be CensoredFixed

The report gives no description here.

LowConfig Uses realtimeFeed Instead Of dataStreamFixed

The report gives no description here.

LowInconsistent AutoCancel ValidationFixed

The report gives no description here.

LowIncorrect Oracle Price EstimateFixed

The report gives no description here.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of GMX’s security record

GMX

Audits38 audits by 1 firmLast audit Apr 2026, by Guardian Audits.

Critical findings1 critical acknowledged, not fixedReported in “GMX VesterCap Updates” by Guardian Audits, Jul 2024. The team acknowledged it.

Open GMX’s security record

Security firm

Guardian Audits

15 projects reviewed · 99 reports · latest Aug 2026

See Guardian Audits’s audits

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.