dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-9831

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A race condition in the shared Extreme Platform ONE IAM Gateway API-key authentication path could, under specific high-concurrency traffic conditions, intermittently allow requests authenticated with an Extreme Platform ONE /IAM-issued API key to receive response data for another tenant. The issue was observed through ExtremeCloud IQ/XIQ API endpoints and validated against both XIQ/XAPI and Extreme Platform ONE /Common Services API paths. XIQ-native tokens and standard OAuth/Bearer JWT authentication were not affected.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A race condition in the Extreme Platform ONE IAM Gateway's API-key authentication path allows cross-tenant data leakage under high-concurrency conditions. The flaw occurs in the shared authentication logic where API-key validated requests can intermittently receive responses belonging to a different tenant. XIQ-native tokens and OAuth/Bearer JWT authentication are unaffected, isolating the issue to the API-key authentication mechanism.

MitigationUntil a vendor patch is available, consider implementing request throttling/rate limiting to reduce the likelihood of triggering the race condition, and monitor API access logs for signs of cross-tenant data exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Extreme Platform ONE IAM Gateway deployment
    Identify if the Extreme Platform ONE IAM Gateway product is deployed in your environment. Check for IAM Gateway services, processes, or documentation referencing 'Extreme Platform ONE' or 'IAM Gateway'. Review network diagrams, asset inventories, or running services on relevant servers.
    Affected if The product is not present in your environment.
  2. Verify API-key authentication is configured
    Examine IAM Gateway configuration files, authentication settings, or API management console to determine if API-key based authentication is enabled. Look for API key generation, storage, or validation configurations specific to the IAM Gateway.
    Affected if API-key authentication is not enabled or not in use; the vulnerability only affects the API-key authentication path.
  3. Check IAM Gateway version against affected releases
    Retrieve the installed IAM Gateway version from the product's admin interface, CLI, or version file (e.g., 'show version', 'about', or check installed packages). Compare your version against any vendor-released patches or release notes addressing CVE-2026-9831.
    Affected if Your version is unpatched and falls within the affected release range (if known), or no patch has been applied.
  4. Inspect API traffic for cross-tenant data anomalies
    Review API access logs, audit trails, or traffic captures for requests where response data does not match the expected tenant context. Look for API key authenticated requests returning data belonging to different tenant identifiers, object ownership, or tenant-scoped resources.
    Affected if Logs show API-key authenticated requests returning data from other tenants, especially during periods of high traffic volume.
  5. Monitor for high-concurrency API access patterns
    Analyze API gateway metrics, load balancer logs, or traffic statistics for periods of elevated concurrent requests to the IAM Gateway API endpoints. Correlate any cross-tenant data anomalies with these high-concurrency windows.
    Affected if Cross-tenant data exposure events occur predominantly during high-concurrency traffic periods, consistent with the race condition trigger.

You are affected if Extreme Platform ONE IAM Gateway is deployed, API-key authentication is enabled, and either your version is unpatched or API logs show cross-tenant data leakage during high-traffic periods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until a vendor patch is available, consider implementing request throttling/rate limiting to reduce the likelihood of triggering the race condition, and monitor API access logs for signs of cross-tenant data exposure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9831 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9831 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data