CVE-2026-46554

NocoDB: Stale Auth Cache After API Token Deletion

LOW
2.3
CVSS Score
Published: June 23, 2026 at 08:30 PM UTC
Updated: June 27, 2026 at 11:42 AM UTC
1 product affected across 1 vendorNocodb

Using nocodb by nocodb?

Get instant alerts when new vulnerabilities affect nocodb - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.3
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2026.04.4
Affected range stops below 2026.04.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2.3LOWGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-613

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card