dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-47386

MEDIUM · 6.3 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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
NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, two concurrent token-exchange requests using the same OAuth authorization code could each mint a distinct valid (access_token, refresh_token) pair, breaking the single-use guarantee that PKCE relies on. This vulnerability is fixed in 2026.05.1.

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

In NocoDB prior to 2026.05.1, a race condition exists in the OAuth token exchange endpoint where two concurrent requests using the same authorization code can both succeed, each minting distinct valid token pairs. This breaks PKCE's single-use guarantee for authorization codes, potentially allowing token theft via request interception or forced concurrent requests.

MitigationUpgrade to NocoDB version 2026.05.1 or later, which implements proper atomic consumption of authorization codes to enforce single-use semantics.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify installed NocoDB version
    Check the version by examining the package.json file in the NocoDB installation directory, or run: npm list nocodb --depth=0 if npm is available, or check the Docker container image tag
    Affected if The version is prior to 2026.05.1 (e.g., 2026.04.x, 2026.03.x, etc.)
  2. Confirm OAuth authentication is configured
    Examine the NocoDB configuration: check environment variables for OAUTH providers (e.g., NC_AUTH_<provider>_CLIENT_ID), or query the nc_auth_providers table in the NocoDB database for enabled OAuth configurations
    Affected if At least one OAuth provider (Google, GitHub, Azure AD, etc.) is configured and enabled in the NocoDB instance
  3. Verify PKCE flow is in use
    Review OAuth client configuration or authentication logs to determine if the Authorization Code flow with PKCE (Proof Key for Code Exchange) is being used for OAuth sign-ins
    Affected if PKCE is enabled in the OAuth provider settings or the application uses authorization codes with code_challenge parameters
  4. Review recent OAuth token exchange logs
    Check application logs for OAuth token endpoint (/api/v1/db/auth/token) activity; look for concurrent or duplicate authorization code usage patterns
    Affected if Logs show multiple successful token exchanges using the same authorization code within a short time window (seconds)
  5. Audit issued OAuth tokens
    Query the nc_access_tokens or similar token storage in the database to identify if multiple access tokens were issued for identical authorization codes
    Affected if Multiple distinct access tokens exist for the same authorization code value

You are affected if NocoDB version is prior to 2026.05.1 AND OAuth authentication with PKCE is configured and actively used in your environment.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NocoDB version 2026.05.1 or later, which implements proper atomic consumption of authorization codes to enforce single-use semantics.

Recommended fix High confidence

2026.05.1

  1. 1. Backup your existing NocoDB database and configuration files before attempting any upgrade.
  2. 2. Review the NocoDB 2026.05.1 release notes for any specific upgrade instructions or prerequisites.
  3. 3. Stop the running NocoDB service.
  4. 4. If using a containerized deployment, pull the new NocoDB image tagged with 2026.05.1 or later.
  5. 5. If using a non-containerized installation, update NocoDB using your package manager or by downloading the new version from the official repository.
  6. 6. Start the NocoDB service with the new version.
  7. 7. Verify that OAuth authentication flows work correctly and that the PKCE single-use guarantee is now enforced.
  8. 8. Monitor logs for any errors related to token exchange or OAuth operations.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47386 — 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-47386 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