CVE-2026-53931

The spreadsheet-import endpoint axiosRequestMake could be used as a generic
HTTP proxy. Before the fix it was reachable unauthenticated, and its
URL-extension allowlist was a regex tested against the full URL string, so
URLs whose query string ended in .csv (for example
https://example.com/robots.txt?.csv) satisfied the gate even though the
underlying request was for robots.txt.

Details

Three layers of protection now apply to the endpoint:

• The controller is decorated with @UseGuards(DataApiLimiterGuard, GlobalGuard)
  and @Acl('fetchViaUrl'), so unauthenticated callers and callers without
  the editor role are rejected before the request body is processed.
• The extension allowlist is tested against url.pathname only. Callers can
  no longer satisfy the regex by appending a .csv suffix to the query
  string.
• The downstream axios call is wired to useAgent(url) from
  request-filtering-agent, which blocks RFC 1918, loopback, link-local,
  and other private destinations at the socket layer.

Credit

This issue was reported by the GitHub Security Lab
(@p-, @m-y-mo).

Unauthenticated callers could previously coerce the NocoDB process to issue
HTTP requests on their behalf, including to internal services reachable from
the host. With the auth gate in place and the pathname-anchored extension
check combined with socket-layer destination filtering, the endpoint is no
longer usable as a generic proxy and can no longer reach private ranges.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Kodem intelligence

1. What is CVE-2026-53931? CVE-2026-53931 is a medium-severity server-side request forgery (SSRF) vulnerability in nocodb (npm), affecting versions <= 0.301.3. No fixed version is listed yet. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. Which versions of nocodb are affected by CVE-2026-53931? nocodb (npm) versions <= 0.301.3 is affected.
3. Is there a fix for CVE-2026-53931? No fixed version is listed for CVE-2026-53931 yet. Monitor the advisory for updates and apply mitigations in the interim.
4. Is CVE-2026-53931 exploitable, and should I be worried? Whether CVE-2026-53931 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-53931 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-53931? No fixed version is listed yet. In the interim: Validate and restrict destination URLs against an allowlist. Block requests to private IP ranges and cloud metadata endpoints.