Continued API access via stale token cache
Published Jun 23, 2026 · Updated Jun 23, 2026
Insufficient token expiration in NocoDB before 2026.04.4 allows remote attackers with deleted API tokens to retain API access. The deletion path removes the token's database row but leaves its token-value keyed authentication-cache entry available to middleware. Exploitation requires possession of a deleted token that was cached before deletion; its existing permissions remain usable for up to three days.
Summary
What happened
Insufficient token expiration in NocoDB before 2026.04.4 allows remote attackers with deleted API tokens to retain API access. The deletion path removes the token's database row but leaves its token-value keyed authentication-cache entry available to middleware. Exploitation requires possession of a deleted token that was cached before deletion; its existing permissions remain usable for up to three days.
The record
- CVE
- CVE-2026-46554
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- NocoDB
- Product
- NocoDB
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2026.04.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo