CVE-2026-33221: 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.
Published Mar 18, 2026 · Updated Jun 9, 2026
Affected packages
github.com/nhost/nhost
- Ecosystem
- Go
- Affected
- < 0.0.0-20260318074820-c4bd53f042d7
- Fixed in
- 0.0.0-20260318074820-c4bd53f042d7
- Check
go list -m github.com/nhost/nhost
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
- Service:
services/storage - File:
services/storage/controller/upload_files.go - Function:
getMultipartFile(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.
Credited to 0xkakash1.
References
- https://github.com/nhost/nhost/security/advisories/GHSA-g9f6-9775-hffm
- https://github.com/nhost/nhost/commit/c4bd53f042d7f568e567e18e2665af81660fce85
- https://nvd.nist.gov/vuln/detail/CVE-2026-33221
- https://github.com/nhost/nhost/pull/4018
- https://github.com/nhost/nhost/releases/tag/[email protected]
- https://github.com/nhost/nhost/releases/tag/storage%400.12.0
- https://github.com/advisories/GHSA-g9f6-9775-hffm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-47671
Nhost CLI local configserver allows cross-origin unauthenticated read/write access to local development configuration and secrets
medium5.4Jun 4, 2026GHSA-7hgr-xvrr-xpw3
nhost has Session Persistence After Password Change
low2.3May 8, 2026CVE-2026-41574
Nhost Vulnerable to Account Takeover via OAuth Email Verification Bypass
critical9.8Apr 18, 2026CVE-2026-34969
Nhost Leaks Refresh Tokens via URL Query Parameter in OAuth Provider Callback
low7.5Apr 1, 2026
