2.1

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-33221

CVE-2026-33221: Nhost Storage Affected by MIME Type Spoofing via Trusted Client Content-Type Header in Storage Upload

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-33221

CVE-2026-33221:

2.1

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
github.com/nhost/nhost	go	< 0.0.0-20260318074820-c4bd53f042d7	0.0.0-20260318074820-c4bd53f042d7

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability exists in the getMultipartFile function located in services/storage/controller/upload_files.go. The root cause of the vulnerability is that the application trusts the Content-Type header sent by the client. The code explicitly checks for the Content-Type header and, if it's not empty or application/octet-stream, it uses the client-provided value directly, skipping server-side MIME type detection. This allows an attacker to upload a file with a misleading MIME type (e.g., uploading an executable file as image/jpeg). The provided patch c4bd53f042d7f568e567e18e2665af81660fce85 confirms this by removing the code block that trusts the client header and ensuring that mimetype.DetectReader is always called to determine the file's true MIME type from its content. Therefore, Controller.getMultipartFile is the vulnerable function that would appear in a runtime profile during exploitation.

Vulnerable functions

Controller.getMultipartFile

services/storage/controller/upload_files.go

The function `getMultipartFile` trusts the client-provided `Content-Type` header. If the header is present and not `application/octet-stream`, the function returns the client's provided MIME type without any server-side verification of the file's actual content. This allows an attacker to upload a file with a spoofed MIME type, which can bypass security controls that rely on file types.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.