FlawAtlas
Search the atlas
CVE-2026-33221 Low

Nhost Storage Affected by MIME Type Spoofing via Trusted Client Content-Type Header in Storage Upload in github.com/nhost/nhost

Nhost Storage Affected by MIME Type Spoofing via Trusted Client Content-Type Header in Storage Upload in github.com/nhost/nhost

Exploit probability 0.2%
Published March 23, 2026
Required by Not available
Last source change March 23, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

1484 explicit affected versions

Go github.com/nhost/nhost
Go github.com/nhost/nhost

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2026:21483-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2026-33221

Nhost is an open source Firebase alternative with GraphQL. Prior to version 0.12.0, 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. This issue has been patched in version 0.12.0.

View original source
Open Source Vulnerabilities GHSA-g9f6-9775-hffm

## 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: ```go 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.

View original source
Open Source Vulnerabilities GO-2026-4759

Nhost Storage Affected by MIME Type Spoofing via Trusted Client Content-Type Header in Storage Upload in github.com/nhost/nhost

View original source

05 / REFERENCES

Further evidence