← Back
CVE-2026-33221
medium
CVSS 5.3
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-343) exists in github.com/nhost/nhost. Attackers reach the vulnerable code path via ``getMultipartFile`` without authentication.
📍 Affected scope
github.com/nhost/nhost — . Attack surface: `getMultipartFile` / `mimetype.DetectReader`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.0-20260318074820-c4bd53f042d7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/nhost/nhost to 0.0.0-20260318074820-c4bd53f042d7ステージング環境で 0.0.0-20260318074820-c4bd53f042d7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/nhost/nhost
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260318074820-c4bd53f042d7"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-33221
- package https://github.com/nhost/nhost
- web https://github.com/nhost/nhost/commit/c4bd53f042d7f568e567e18e2665af81660fce85
- web https://github.com/nhost/nhost/pull/4018
- web https://github.com/nhost/nhost/releases/tag/storage%400.12.0
- web https://github.com/nhost/nhost/security/advisories/GHSA-g9f6-9775-hffm
- web https://github.com/nhost/nhost/releases/tag/[email protected]
- web https://github.com/advisories/GHSA-g9f6-9775-hffm