dbcve.org
CWE-441Weakness · CWE-441

CVE-2026-53931

MEDIUM · 6.9 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NocoDB's spreadsheet-import endpoint (axiosRequestMake) was accessible without authentication and could be abused as an HTTP proxy. The vulnerability stemmed from a flawed allowlist regex that only checked if a URL's query string ended in .csv, allowing attackers to proxy requests to arbitrary internal or external URLs by appending ?anything.csv to the request.

MitigationUpgrade to NocoDB version 2026.05.1 or later. If immediate patching is not feasible, restrict access to the spreadsheet-import endpoint at the network level or implement additional authentication controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NocoDB installation
    Locate NocoDB by checking running processes, Docker containers, or installation directories. Common paths: /usr/local/nocodb, /opt/nocodb, or Docker container named 'nocodb'. Check for 'nocodb' in process list with command: ps aux | grep -i nocodb or docker ps | grep -i nocodb
    Affected if NocoDB is present in the environment
  2. Determine installed NocoDB version
    Check version file in installation directory (version.js, package.json), or query the API endpoint /api/v1/version if available, or inspect Docker image tags. Compare against the fixed version 2026.05.1
    Affected if Installed version is earlier than 2026.05.1
  3. Verify spreadsheet-import endpoint is network-accessible
    Attempt a curl request to the axiosRequestMake endpoint. Default path is /api/v1/spreadsheet-import/axiosRequestMake or similar. From an unauthorized network location, send: curl -s -o /dev/null -w '%{http_code}' <nocodb-url>/api/v1/spreadsheet-import/axiosRequestMake
    Affected if Endpoint returns any HTTP response (even 404/500) indicating it is reachable
  4. Test for proxy abuse vulnerability
    Send a request to the endpoint with a crafted query parameter ending in .csv to an arbitrary URL. Example: curl '<target>/api/v1/spreadsheet-import/axiosRequestMake?url=http://example.com/test.csv' -v. If the server attempts to fetch or returns content from example.com, the vulnerability is present
    Affected if The endpoint successfully proxies the request or returns content from the arbitrary URL specified in the query parameter

A user is affected if NocoDB version is earlier than 2026.05.1 AND the spreadsheet-import endpoint is network-accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NocoDB version 2026.05.1 or later. If immediate patching is not feasible, restrict access to the spreadsheet-import endpoint at the network level or implement additional authentication controls.

Recommended fix High confidence

2026.05.1

  1. Backup the current NocoDB installation and database before proceeding with any changes
  2. Upgrade NocoDB to version 2026.05.1 or later using the appropriate installation method (npm, Docker, or direct download)
  3. After upgrading, verify the axiosRequestMake endpoint is no longer accessible as an unauthenticated HTTP proxy
  4. Confirm that the spreadsheet-import functionality still works correctly for legitimate .csv imports
  5. Review access logs to ensure no unauthorized proxy requests were made during the vulnerable period

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53931 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53931 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data