CVE-2026-53927
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 · uneditedNocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-fetch endpoint (axiosRequestMake) accepted URLs whose path contained a permitted extension anywhere in the string, and applied a hand-rolled regex blocklist that omitted 127.0.0.0/8 and 169.254.0.0/16, allowing the cloud-metadata endpoint to be reached with a crafted URL 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 confidenceNocoDB's spreadsheet-fetch endpoint (axiosRequestMake) is vulnerable to Server-Side Request Forgery (SSRF). The endpoint accepts URLs with permitted extensions and uses a hand-rolled regex blocklist that fails to block the 127.0.0.0/8 and 169.254.0.0/16 IP ranges, allowing attackers to access cloud-metadata services like AWS EC2 metadata at 169.254.169.254.
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
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NocoDB installation versionLocate the NocoDB version by checking the package.json file in the installation directory, the Docker image tag, or by querying the NocoDB API health/version endpoint if exposedAffected if The installed version is earlier than 2026.05.1 (e.g., 2025.x, 2024.x, or older release lines)
-
Verify spreadsheet-fetch endpoint is accessibleConfirm that the axiosRequestMake endpoint (typically at /api/v1/tables/{id}/spreadsheet-fetch or similar spreadsheet-related API path) is reachable without authentication or with valid user credentialsAffected if The spreadsheet-fetch endpoint is enabled and accessible to the attacker (either anonymously or via valid user session)
-
Check for cloud metadata network exposureReview network configuration to determine if the NocoDB server can make outbound HTTP/HTTPS requests to cloud metadata IP addresses, particularly 169.254.169.254 (AWS) or similar cloud provider metadata endpointsAffected if The server running NocoDB has network access to 169.254.0.0/16 or 127.0.0.0/8 IP ranges and can initiate outbound HTTP connections to those addresses
You are affected if NocoDB version is before 2026.05.1 AND the spreadsheet-fetch endpoint is accessible AND the server has network access to cloud metadata IP ranges.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade NocoDB to version 2026.05.1 or later, which includes a fix for this SSRF vulnerability.
2026.05.1
- Upgrade NocoDB to version 2026.05.1 or later to address the SSRF vulnerability in the spreadsheet-fetch endpoint (axiosRequestMake)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53927 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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