NocoDB has Blind SSRF via Unvalidated HEAD Request in uploadViaURL Functionality
Summary
A blind Server-Side Request Forgery (SSRF) vulnerability exists in the uploadViaURL functionality due to an unprotected HEAD request. While the subsequent file retrieval logic correctly enforces SSRF protections, the initial metadata request executes without validation.
This allows limited outbound requests to arbitrary URLs before SSRF controls are applied.
Vulnerability Details
The uploadViaURL() function issues an axios.head() request to retrieve metadata (content type, content length, and final URL after redirects). This request is performed without SSRF filtering.
Although the actual file download is protected by request filtering, the initial HEAD request occurs prior to these checks and can be triggered with an attacker-controlled URL.
Vulnerable Code
if (!url.startsWith('data:')) {
response = await axios.head(url, { maxRedirects: 5 });
mimeType = response.headers['content-type']?.split(';')[0];
size = response.headers['content-length'];
finalUrl = response.request.res.responseUrl;
}
Impact
The impact of this issue is limited due to the following constraints:
- Only
HEADrequests are affected (no response body is returned) - No direct exfiltration of response data occurs
- The subsequent file-fetching logic enforces SSRF protections
However, the vulnerability may still allow:
- Blind SSRF via outbound
HEADrequests - Limited internal service probing (reachability and response behavior)
- Interaction with sensitive internal endpoints that respond to
HEADrequests
This issue does not provide arbitrary data access or full internal network compromise on its own.
Severity
Moderate
The vulnerability is limited in scope and impact:
- Only
HEADrequests are affected - No response body or sensitive data is directly returned
- The actual file download logic enforces SSRF protections
While the issue permits blind outbound requests to attacker-controlled URLs, it does not enable direct data exfiltration or full internal network compromise on its own.
Proof of Concept
curl -X POST 'http://localhost:8080/api/v2/storage/upload-by-url' \
-H 'Content-Type: application/json' \
-H 'xc-auth: <token>' \
-d '[{
"url": "http://169.254.169.254/latest/meta-data/",
"fileName": "test.txt"
}]'
This request causes the server to issue an unfiltered HEAD request before SSRF protections are applied.
Acknowledgements
This issue was first identified and responsibly disclosed by Faizan Raza of Kolega.dev as part of a security assessment using Kolega.dev Deep Code Scan, including validation and fix recommendations.
NocoDB also acknowledges Neel B for independently reporting the same issue prior to publication.
NocoDB thanks Kolega.dev for their contribution to improving the security posture of the project.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | nocodb | < 0.301.0 | 0.301.0 |
Referencias
- Vector CVSS
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N- Debilidad (CWE)
CWE-918- Plataforma
- npm
- Paquete
nocodb- Publicada
- 28.01.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-xr7v-j379-34v9 - CC BY 4.0
Historial de vulnerabilidades: nocodb
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 54
- Primera → última
- 06.2022 06.2026
- Sin corrección
- 13
- Explotada en ataques
- 0
Distribución por gravedad
- Alta 7
- Media 41
- Baja 6
Divulgaciones por año
- 2022: 5
- 2023: 2
- 2024: 3
- 2025: 1
- 2026: 43
-
NocoDB has Blind SSRF via Unvalidated HEAD Request in uploadViaURL Functionality esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.