CVE-2026-47671: Nhost CLI missing authentication in local configserver

CVE-2026-47671 · Severity: medium · CVSS 5.4 · Published 2026-07-21

Nhost is an open-source development platform used as an alternative to Firebase. In affected versions of its command-line interface (CLI), a background service used during local development fails to properly restrict access. This allows malicious websites visited by a developer to steal sensitive project secrets—such as admin keys and JWT signing keys—or modify local configuration files, potentially leading to a full compromise of the development environment.

Technologies: github.com/nhost/nhost (Go), Nhost\. Vendors: Go, Nhost.

Quick answers

Is CVE-2026-47671 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47671 being exploited in the wild.
How severe is CVE-2026-47671?
Medium severity, with a CVSS score of 5.4, published 21 July 2026.
Which products and versions are affected?
github.com/nhost/nhost (Go) < 0.0.0-20260518172022-e407511627d2, SEMVER:introduced=0,fixed=0.0.0-20260518172022-e407511627d2; Nhost\ < 0.0.0-20260518172022-e407511627d2.
Is there a fix for CVE-2026-47671?
Yes. github.com/nhost/nhost (Go): upgrade to 0.0.0-20260518172022-e407511627d2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47671 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-47671?
Check whether you run github.com/nhost/nhost (Go) or Nhost\ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/nhost/nhost (Go): upgrade to 0.0.0-20260518172022-e407511627d2 or later
    go get github.com/nhost/nhost@v0.0.0-20260518172022-e407511627d2

Technical details

A vulnerability in the hidden `nhost configserver` component, triggered by the `nhost dev` command, stems from missing authentication (CWE-306) and overly permissive CORS policies. The Mimir GraphQL API is exposed with dummy authorization directives, allowing any process capable of reaching the developer's localhost—including a browser executing code from an arbitrary origin—to query or mutate local configuration. Attackers can exploit this via Cross-Origin Resource Sharing (CORS) to read sensitive data like project admin secrets, JWT signing keys, and webhook secrets, or to overwrite the local `.secrets` file. The fix in version 1.46.0 introduces regex-validated origin checks, redacts secrets in memory, and implements a per-project random UUIDv4 for authentication.

Affected products

  • Nhost CLI < 1.46.0

Identifiers

  • CVE-2026-47671
  • GHSA-64cj-qvx5-m4f3
  • GO-2026-5166

Timeline

  • 2026-05-18: patched: Fix committed to main branch
  • 2026-05-19: advisory: Release cli@1.46.0 published
  • 2026-07-21: disclosed: CVE-2026-47671 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.