Vulnerability in github.com/nhost/nhost (CVE-2026-33221)
Summary
Vulnerability in github.com/nhost/nhost (CVE-2026-33221). Risk of unauthorized operations or information disclosure. Exploitable via getMultipartFile. Mitigation: upgrade to 0.0.0-20260318074820-c4bd53f042d7 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33221 has been found in github.com/nhost/nhost.
Attackers can target a specific entry point like getMultipartFile over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/nhost/nhost to 0.0.0-20260318074820-c4bd53f042d7 or later.
If unsure, ask your IT team or search "github.com/nhost/nhost CVE-2026-33221" on the vendor's site.
CVE-2026-33221 (github.com/nhost/nhost) — CWE-343 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: getMultipartFile / mimetype.DetectReader
Patched: 0.0.0-20260318074820-c4bd53f042d7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-343) exists in github.com/nhost/nhost. Attackers reach the vulnerable code path via getMultipartFile without authentication.
Check the vendor advisory for the affected versions of github.com/nhost/nhost. Attack surface: getMultipartFile / mimetype.DetectReader.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260318074820-c4bd53f042d7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/nhost/nhost' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/nhost/nhost' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/nhost/nhostを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/nhost/nhost to 0.0.0-20260318074820-c4bd53f042d7ステージング環境で 0.0.0-20260318074820-c4bd53f042d7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com