CVE-2026-53931: NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint
Summary 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.
Published Jun 17, 2026 · Updated Jul 20, 2026
Affected packages
nocodb
- Ecosystem
- npm
- Affected
- <= 0.301.3
- Fixed in
- No patched version yet
- Check
npm ls nocodb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.pathnameonly. Callers can no longer satisfy the regex by appending a.csvsuffix to the query string. - The downstream axios call is wired to
useAgent(url)fromrequest-filtering-agent, which blocks RFC 1918, loopback, link-local, and other private destinations at the socket layer.
Impact
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.
Credit
This issue was reported by the GitHub Security Lab (@p-, @m-y-mo).
Credited to p-.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-53927
NocoDB: Server-Side Request Forgery via Spreadsheet Fetch URL
medium5.1No fixJun 17, 2026CVE-2026-53928
NocoDB: Refresh Tokens Persist Through Password Recovery
medium6.3No fixJun 17, 2026CVE-2026-53929
NocoDB: Stored Cross-Site Scripting via Secure Attachment
medium5.1No fixJun 17, 2026CVE-2026-53930
NocoDB: Server-Side Request Forgery via Base Migration URL
medium5.1No fixJun 17, 2026CVE-2026-47279
NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints
medium6.9Jun 5, 2026CVE-2026-47375
NocoDB: Postgres SQL Injection in Formula `ARRAYSORT`
medium6.0Jun 5, 2026
