Authenticated internal service probing via unfiltered HEAD request
Published Jan 28, 2026 · Updated Jan 28, 2026
SSRF in uploadViaURL in NocoDB before 0.301.0 allows remote authenticated users to probe network services via crafted URLs. The function sends axios.head() to an attacker-controlled URL, follows up to five redirects, and reads metadata before applying the download path SSRF filter. Low-privileged API access is required; the blind request returns no body but reveals reachability and response behavior and can contact endpoints that act on HEAD.
Summary
What happened
SSRF in uploadViaURL in NocoDB before 0.301.0 allows remote authenticated users to probe network services via crafted URLs. The function sends axios.head() to an attacker-controlled URL, follows up to five redirects, and reads metadata before applying the download path SSRF filter. Low-privileged API access is required; the blind request returns no body but reveals reachability and response behavior and can contact endpoints that act on HEAD.
The record
- CVE
- CVE-2026-24767
- Published
- Jan 28, 2026
- Updated
- Jan 28, 2026
- Vendor
- NocoDB
- Product
- NocoDB
- Classifications
- CWE-918, T1046
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2026CVE publishedPublication date reported by the CVE source.
- Jan 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.301.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Vendor curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo