# CVE-2026-121736: NocoDB 0.300.0 before 2026.08.0 Unauthenticated OAuth Authorization Code Creation


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-532v-ccph-m3xg, GHSA-mc8q-8prc-j4hf

## What is CVE-2026-121736?

CVE-2026-121736 is a medium-severity vulnerability in nocodb, published on 3 Nov 2026. 

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-121736?


## How do I fix CVE-2026-121736?

No fix has been published for CVE-2026-121736 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121736 being exploited?

There is no known exploitation of CVE-2026-121736 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121736 and fix it if it is affected.

What it is: CVE-2026-121736 is a medium-severity vulnerability in nocodb, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121736 in the wild and no public exploit code.

Affected product: nocodb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121736/ (Markdown: https://insights.sbomify.com/CVE-2026-121736/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121736
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121736
- OSV: https://osv.dev/vulnerability/CVE-2026-121736

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121736/
Summaries are generated and may contain mistakes; the official description above is the record.