Skip to main content
← Vulnerabilities

NocoDB 0.300.0 before 2026.08.0 Unauthenticated OAuth Authorization Code Creation

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2026.08.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2026.08.0.

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

CVE-2026-121736 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects nocodb; fixed in 2026.08.0.

Published
Last modified
Published
Not listed in CISA KEV
24/100 · provisional
Fix
Fixed in 2026.08.0
None on Exploit-DB, Metasploit or GitHub

Summary

NocoDB, an open-source no-code database platform, is affected by this flaw. An unauthenticated attacker can abuse its OAuth authorization endpoint to create large numbers of authorization code records without logging in, which could lead to database bloat and resource exhaustion on the server.

Read the original description

NocoDB 0.300.0 before 2026.08.0 contains a missing authentication vulnerability in the POST /api/v2/oauth/authorize handler that allows unauthenticated attackers to create OAuth authorization codes. Attackers can send anonymous requests with client_id, redirect_uri and approved=true to insert unbounded ownerless authorization code records, limited only by rate limiting.

What to do

  • Upgrade to a fixed version: 2026.08.0.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • nocodb nocodb

    From 0.300.0 · fixed in 2026.08.0

Evidence 6

  1. Advisory
  2. Patch
  3. Repository
  4. Repository
  5. Repository
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121736

Is CVE-2026-121736 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121736?

nocodb: from 0.300.0 before 2026.08.0.Source: cve.now feed data

How do I fix CVE-2026-121736?

Upgrade to a fixed version: 2026.08.0.Source: cve.now feed data