cve.bz

CVE-2026-126276 NocoDB before 2026.08.1 Client Authentication Bypass via OAuth Token Exchange

8.2 highEPSS 0.2%

High (8.2) in nocodb nocodb. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
NocoDB before 2026.08.1 contains an authentication bypass vulnerability in oauth-token.service.ts that treats PKCE as a substitute for confidential client authentication, skipping client secret verification when omitted. Attackers holding a captured authorization code and PKCE verifier can mint access tokens and 60-day refresh tokens for a confidential client without knowing its secret.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

CVSS 3.1

6.3 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126276 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126276?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126276?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126276 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126276

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126276](https://cve.bz/cve/badge/CVE-2026-126276.svg)](https://cve.bz/cve/CVE-2026-126276)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126276"><img src="https://cve.bz/cve/badge/CVE-2026-126276.svg" alt="CVE-2026-126276"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nocodbbefore 2026.08.1

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON