github.com/nhost/nhost
Affected
- introduced
0, fixed0.0.0-20260318074820-c4bd53f042d7(semver)
Fixed versions
0.0.0-20260318074820-c4bd53f042d7
Fix
- Fixed version
0.0.0-20260318074820-c4bd53f042d7go get github.com/nhost/[email protected]
Advisory
Also known as: CVE-2026-33221, GO-2026-4759
Nhost Storage Affected by MIME Type Spoofing via Trusted Client Content-Type Header in Storage Upload
Summary
The storage service's file upload handler trusts the client-provided Content-Type header without performing server-side MIME type detection. This allows an attacker to upload files with an arbitrary MIME type, bypassing any MIME-type-based restrictions configured on storage buckets.
Affected Component
services/storageservices/storage/controller/upload_files.gogetMultipartFile (lines 48-70)Root Cause
In getMultipartFile, if the client provides a non-empty Content-Type header that isn't application/octet-stream, the function returns it as-is without performing content-based detection:
contentType := file.header.Header.Get("Content-Type")
if contentType != "" && contentType != "application/octet-stream" {
return fileContent, contentType, nil // skip detection entirely
}
// mimetype.DetectReader only reached if client sends no Content-Type
// or sends application/octet-stream
mt, err := mimetype.DetectReader(fileContent)
Impact
Incorrect MIME type in file metadata. The MIME type stored in file metadata reflects what the client claims rather than what the file actually contains. Any system consuming this metadata (browsers, CDNs, applications) may handle the file incorrectly based on the spoofed type.
Suggested Fix
Always detect MIME type from file content using mimetype.DetectReader, ignoring the client-provided Content-Type header entirely.
Low Basis: The source's own band: LOW
0, fixed 0.0.0-20260318074820-c4bd53f042d7 (semver)0.0.0-20260318074820-c4bd53f042d7
0.0.0-20260318074820-c4bd53f042d7go get github.com/nhost/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0