CVE-2026-47386
Received Received - Intake
Authentication Bypass via OAuth Code Reuse in NocoDB

Publication date: 2026-06-23

Last updated on: 2026-06-23

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-23
Last Modified
2026-06-23
Generated
2026-06-24
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
CVE-2026-47386
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
nocodb nocodb to 2026.05.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in NocoDB versions prior to 2026.05.1. It involves the OAuth authorization code flow where two concurrent token-exchange requests using the same authorization code can each generate a distinct valid pair of access and refresh tokens. This breaks the single-use guarantee of the authorization code, which PKCE (Proof Key for Code Exchange) relies on to ensure security.

Impact Analysis

The impact of this vulnerability is that an attacker or malicious actor could potentially use the same OAuth authorization code multiple times to obtain multiple valid access and refresh tokens. This undermines the security of the OAuth flow, potentially allowing unauthorized access to protected resources or user data.

Mitigation Strategies

To mitigate this vulnerability, you should update NocoDB to version 2026.05.1 or later, where the issue with concurrent token-exchange requests using the same OAuth authorization code has been fixed.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47386. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart