CVE-2026-116120: NocoDB PublicApiLimiterGuard signup UserRefreshToken.deleteAllUserToken allocation of resources
A vulnerability was determined in NocoDB up to 2026.07.0. This vulnerability affects the function UserRefreshToken.deleteAllUserToken of the file /auth/user/signup of the component PublicApiLimiterGuard. This manipulation causes allocation of resources. The attack is possible to be carried out remotely. The attack is considered to have high complexity. It is stated that the exploitability is difficult. Code-verified absence of in-app rate limiting on the unauthenticated signup and password-forgot endpoints and per-request refresh/OAuth token invalidation, but the vendor documents the pass-through limiter as intentional design. The vendor deleted the GitHub issue for this vulnerability without any explanation. Afterwards the vendor was contacted early about this disclosure via email but did not respond in any way.
Affected Software
Event History
Frequently Asked Questions
Which endpoints are implicated by the missing in-application rate limiting?
The unauthenticated signup and password-forgot endpoints are identified as lacking in-app rate limiting. The affected signup path includes PublicApiLimiterGuard and UserRefreshToken.deleteAllUserToken.
Does exploitation require authentication or user interaction?
No authentication or user interaction is required according to the provided vector. The attack can be conducted remotely, but is considered high complexity and difficult to exploit.
What is the potential impact?
The issue can cause resource allocation, with low assessed impact to confidentiality, integrity, and availability. Per-request refresh or OAuth token invalidation is also identified in the affected behavior.
Is the lack of rate limiting necessarily unintended behavior?
The vendor documents the pass-through limiter as intentional design. However, the reported issue describes code-verified absence of in-app rate limiting on the specified unauthenticated endpoints.