NocoDB: Stale Auth Cache After API Token Deletion

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · 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 · score source

EPSS

• CVE-2026-46554: 0.31% estimated exploitation activity in the next 30 days; percentile 24.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

21 May 2026, 20:39 UTC

Last modified by the source

20 Jul 2026, 21:30 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f76x-f9vj-92jv

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f76x-f9vj-92jv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46554

Advisory: NocoDB: Stale Auth Cache After API Token Deletion
IDs: CVE-2026-46554, GHSA-f76x-f9vj-92jv
Record: https://patchnext.com/advisories/cve-2026-46554 (revision 3, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected <= 0.301.3

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f76x-f9vj-92jv (OSV record GHSA-f76x-f9vj-92jv lists affected ranges: npm nocodb >=0 <=0.301.3)
- Verified: https://github.com/advisories/GHSA-f76x-f9vj-92jv (GitHub-reviewed advisory GHSA-f76x-f9vj-92jv lists affected ranges: npm nocodb >=0 <=0.301.3)

Commands are suggestions: review each one before running it.