# CVE-2026-130695: NocoDB before 2026.10.1 Authentication Bypass via Revoked OAuth Access Tokens


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-5c8g-mjc2-7gwq, GHSA-r872-6prr-v2jc

## What is CVE-2026-130695?

CVE-2026-130695 is a medium-severity vulnerability in nocodb, published on 18 Nov 2026. 

### Official description

NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows holders of revoked OAuth access tokens to authenticate as first-party sessions by presenting them through the session header. Attackers can bypass revocation, client-existence, route allowlist and granted_resources scope checks to modify victim profiles, upload to storage, and force global sign-outs.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

Upgrade nocodb to 2026.10.1 or later. The advisory says that version fixes it.

## Is CVE-2026-130695 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130695 is a medium-severity vulnerability in nocodb, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130695 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-130695/ (Markdown: https://insights.sbomify.com/CVE-2026-130695/index.md)
```

## Sources

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

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