CVE-2026-47386: NocoDB OAuth authorization code race condition

CVE-2026-47386 · Severity: medium · CVSS 4 · Published 2026-06-23

NocoDB is an open-source platform that turns databases into smart spreadsheets. A security flaw in its login process could allow an attacker who intercepts certain temporary login codes to gain unauthorized, long-term access to a user's account. This occurs because the system fails to properly invalidate a login code if two requests are made at the exact same time.

Technologies: nocodb (npm). Vendors: npm.

Quick answers

Is CVE-2026-47386 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47386 being exploited in the wild.
How severe is CVE-2026-47386?
Medium severity, with a CVSS score of 4, published 23 June 2026.
Which products and versions are affected?
nocodb (npm) <= 2026.05.0, ECOSYSTEM:introduced=0,fixed=2026.05.1.
Is there a fix for CVE-2026-47386?
Yes. nocodb (npm): upgrade to 2026.05.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47386 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47386?
Check whether you run nocodb (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • nocodb (npm): upgrade to 2026.05.1 or later
    npm install nocodb@2026.05.1

Technical details

A race condition (CWE-362) exists in the OAuth token-exchange flow of NocoDB. The application originally performed an unconditional update to mark an authorization code as used only at the end of the request path. An attacker who observes an authorization code and PKCE verifier can perform concurrent requests to bypass the single-use guarantee, resulting in the generation of multiple valid access and refresh token pairs. The fix introduces an atomic compare-and-swap operation (claimByCode) to ensure only the first request succeeds. This issue is resolved in version 2026.05.1.

Affected products

  • NocoDB NocoDB < 2026.05.1

Identifiers

  • CVE-2026-47386
  • GHSA-8m7c-hf24-5g47

Timeline

  • 2026-06-04: advisory: GitHub Security Advisory published
  • 2026-06-23: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.