Vulnerability in github.com/nhost/nhost (CVE-2026-47671)
Summary
Vulnerability in github.com/nhost/nhost (CVE-2026-47671). Risk of unauthorized operations or information disclosure. Exploitable via configserver. Mitigation: upgrade to 0.0.0-20260518172022-e407511627d2 or later.
Original description
The description as published by the source.
Nhost is an open source Firebase alternative with GraphQL. In versions of Nhost CLI prior to 1.46.0, the hidden nhost configserver used by nhost dev exposes the Mimir GraphQL API with dummy authorization directives and permissive CORS. When a developer is running the local development environment, any process that can reach the developer's localhost service, including a web page loaded from an arbitrary origin, can query the configserver for local Nhost configuration and secrets and can mutate the local .secrets file. This impacts developers using nhost dev: project admin secrets, JWT signing keys, webhook secrets, Grafana credentials, and custom environment variables can be read, and attacker-controlled secrets can be written to the local development project. Version 1.46.0 of Nhost CLI contains a fix.
Source: GitHub Security Advisories (Global) 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-47671 has been found in github.com/nhost/nhost.
Attackers can target a specific entry point like configserver over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade github.com/nhost/nhost to 0.0.0-20260518172022-e407511627d2 or later.
If unsure, ask your IT team or search "github.com/nhost/nhost CVE-2026-47671" on the vendor's site.
CVE-2026-47671 (github.com/nhost/nhost) — CWE-306 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: configserver / graph.SetupRouter / dummyMiddleware / dummyMiddleware2
Patched: 0.0.0-20260518172022-e407511627d2 — 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-306) exists in github.com/nhost/nhost. Attackers reach the vulnerable code path via configserver without authentication.
Check the vendor advisory for the affected versions of github.com/nhost/nhost. Attack surface: configserver / graph.SetupRouter / dummyMiddleware / dummyMiddleware2.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260518172022-e407511627d2.
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-20260518172022-e407511627d2ステージング環境で 0.0.0-20260518172022-e407511627d2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com