GHSA-f76x-f9vj-92jv

Suggest an improvement
Source
https://github.com/advisories/GHSA-f76x-f9vj-92jv
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-f76x-f9vj-92jv/GHSA-f76x-f9vj-92jv.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-f76x-f9vj-92jv
Aliases
  • CVE-2026-46554
Published
2026-05-21T20:39:53Z
Modified
2026-05-21T20:45:09.203016498Z
Severity
  • 2.3 (Low) CVSS_V4 - 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 CVSS Calculator
Summary
NocoDB: Stale Auth Cache After API Token Deletion
Details

Summary

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.

Details

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.

Impact

Tokens revoked through the UI or API continued to grant access during the cache TTL, breaking the operator's expected security guarantee that deletion is immediate.

Credit

This issue was reported by @bugbunny-research.

Database specific
{
    "nvd_published_at": null,
    "cwe_ids": [
        "CWE-613"
    ],
    "github_reviewed": true,
    "severity": "LOW",
    "github_reviewed_at": "2026-05-21T20:39:53Z"
}
References

Affected packages

npm / nocodb

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Last affected
0.301.3

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-f76x-f9vj-92jv/GHSA-f76x-f9vj-92jv.json"