CVE-2026-46554
LowCVSS 2.3Exploitation Probability (EPSS)
Low risk10th percentile - higher than 10% of all known CVEs
Summary
NocoDB, software for building databases as spreadsheets, had an issue with deleting API tokens. Prior to version 2026.04.4, deleted tokens continued to authenticate requests until their cache entry expired.
Risk Assessment
Organizations could be exposed to unauthorized access as deleted tokens could be used for authentication for up to three days.
Recommendation
It is recommended to update NocoDB to version 2026.04.4 to eliminate this vulnerability and ensure that deleted tokens cannot be used for authentication.
Other vulnerabilities in NocoDB
See all- CVE-2023-35843High
NocoDB through 0.106.0 (or 0.109.1) has a path traversal vulnerability that allows an unauthenticated attacker to access arbitrary files on the server by manipulating the path parameter of the /download route.
- CVE-2026-119715Medium
NocoDB before 2026.08.0 contains a clickjacking vulnerability because no X-Frame-Options or CSP frame-ancestors headers are sent, allowing any origin to frame the authenticated interface. Attackers can overlay a signed-in user's session from a malicious page, tricking clicks that modify or delete records, change sharing settings, or invite collaborators.
- CVE-2026-116123Low
In NocoDB up to 2026.07.0, the validatePassword function in /auth/user/signup does not adequately restrict excessive authentication attempts. The flaw enables a remote attack of high complexity, and the vendor describes this behavior as intentional. The GitHub issue was deleted without explanation and email contact went unanswered.
- CVE-2026-116122Low
In NocoDB up to 2026.07.0, the AuthService.validateUser function in the Sign-in Endpoint component, when the salt argument is manipulated, leads to information disclosure. The attack can be performed remotely, is rated high complexity, and is considered difficult to exploit. The vendor deleted the GitHub issue without explanation and did not respond to email contact.
- CVE-2026-116121Low
In NocoDB up to 2026.08.0, unspecified processing in users.service.ts within the Registration component leads to a race condition. The attack can be performed remotely, requires a high level of complexity, and is assessed as difficult to exploit. The vendor deleted the GitHub issue without explanation and did not respond to email contact.
- CVE-2026-116120Medium
In NocoDB up to 2026.07.0, the UserRefreshToken.deleteAllUserToken function in /auth/user/signup, part of the PublicApiLimiterGuard component, allows uncontrolled resource allocation. The absence of in-app rate limiting on unauthenticated signup and password-forgot endpoints enables a remote attack of high complexity. The vendor considers the limiter pass-through intentional design and deleted the issue without explanation.
- CVE-2026-116119Medium
A vulnerability was found in NocoDB up to version 2026.08.0 in an unknown part of the users.service.ts file within the Password-Reset Flow component. The manipulation results in a race condition that can be exploited remotely. The vendor deleted the GitHub issue without explanation and did not respond to disclosure contact.
- CVE-2026-53931Medium
NocoDB prior to version 2026.05.1 had a vulnerability that allowed the spreadsheet-import endpoint axiosRequestMake to be used as a generic HTTP proxy. This endpoint was accessible unauthenticated, enabling unauthorized access.
- CVE-2026-53930Medium
NocoDB prior to version 2026.05.1 had a vulnerability in the base-migration endpoint that accepted a caller-supplied URL without enforcing protocol or destination. This allowed scheme abuse and probing of internal HTTP destinations.
- CVE-2026-53929Medium
NocoDB prior to version 2026.05.1 allowed authenticated uploaders to deliver .html or .svg attachments that were rendered inline in the browser instead of forcing a download. The issue stemmed from a mismatch in how response headers were handled, leading to automatic rendering of these files.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

