---
id: "CVE-2026-126283"
page: "https://infrastack.ai/live/CVE-2026-126283"
kind: "vulnerability"
aliases: ["CVE-2026-126283"]
title: "NocoDB: base-scoped API tokens reach every base the owner has"
severity: "high"
cvss: 8.8
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "api-tokens", "nocodb", "self-hosted"]
not_affected_if: ["no-api-tokens", "version-2026.08.0-or-later"]
published_at: "2026-11-13T10:17:31+00:00"
first_seen_at: "2026-11-13T10:47:13+00:00"
updated_at: "2026-11-13T10:49:04+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126283", "first_seen_at": "2026-11-13T10:47:13+00:00"}]
exploit_sources: []
---

# NocoDB: base-scoped API tokens reach every base the owner has

Link for people: https://infrastack.ai/live/CVE-2026-126283 (this .md is for agents)

NocoDB before 2026.08.0 does not store or check the base a token was issued for, so a base-scoped API token works as an account-wide credential. An attacker holding a leaked token can read, change and delete records in every base the token owner belongs to, including bases joined later.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the NocoDB version with `unknown` in the running instance; the sources do not give a command.
- Review API tokens issued in the workspace and treat any token that may have leaked as exposed.

## Fix

- NocoDB: move to `2026.08.0` or later.

## Timeline

- 2026-11-13T10:47:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126283

## Documents

- [advisory] Vendor advisory: github.com https://github.com/nocodb/nocodb/security/advisories/GHSA-7395-6gh4-5q8p
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/nocodb-before-2026.08.0-incorrect-authorization-via-base-scoped-api-tokens

## From the sources

NocoDB before 2026.08.0 contains an incorrect authorization vulnerability that lets base-scoped API tokens act as account-wide credentials because the token's base_id is never stored or checked. Attackers holding a leaked token can read, write and delete records on every base the token owner belongs to, including bases joined later.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_