Vulnerability · Published Jun 23, 2026 · Assigned by GitHub_M

CVE-2026-46554NocoDB: Stale Auth Cache After API Token Deletion

Low 2.3

In plain English

A low-severity security flaw in nocodb from nocodb. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 24% of all known vulnerabilities).

Severity (CVSS 4.0)2.3Low
Exploit odds (30 days)0.3%top 75.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

NocoDB is software for building databases as spreadsheets. Prior to 2026.04.4, deleted API tokens continued to authenticate requests until their cache entry expired, because the auth cache was not invalidated by token value at deletion time. The API token deletion path removed the database row but did not evict the token-value keyed entry from the auth cache. The auth middleware therefore continued to accept the deleted token until the cache entry aged out, leaving a deletion-to-revocation window of up to three days. This vulnerability is fixed in 2026.04.4.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmnocodbno fix listedGHSA-f76x-f9vj-92jv

Affected products (as reported)

VendorProductVersions
nocodb nocodb < 2026.04.4

Weakness: CWE-613 · Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References