Quick answers
- Is CVE-2026-116120 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116120 being exploited in the wild.
- How severe is CVE-2026-116120?
- Medium severity, with a CVSS score of 5.6, published 26 October 2026.
- Which products and versions are affected?
- NocoDB up to 2026.07.0.
- Is there a fix for CVE-2026-116120?
- No fixed version is recorded yet. Implement manual rate limiting at the application or infrastructure level on the signup, password-forgot, and token endpoints; alternatively, restrict access to these endpoints through a WAF or reverse proxy. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-116120 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116120?
- Check whether you run NocoDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Implement manual rate limiting at the application or infrastructure level on the signup, password-forgot, and token endpoints; alternatively, restrict access to these endpoints through a WAF or reverse proxy.
Technical details
The vulnerability exists in the PublicApiLimiterGuard component, specifically affecting the UserRefreshToken.deleteAllUserToken function in the /auth/user/signup endpoint. The issue involves insufficient rate limiting on unauthenticated endpoints (signup, password-forgot) and per-request token invalidation, allowing an attacker to trigger resource exhaustion remotely through repeated API calls. While attack complexity is high and exploitability is considered difficult, the lack of authentication requirements makes remote exploitation feasible.
Affected products
- NocoDB NocoDB up to 2026.07.0
Timeline
- 2026-10-26: disclosed