# CVE-2026-47671: Nhost CLI local configserver allows cross-origin unauthenticated read/write access to local development configuration and secrets

> Attackers can read and modify local Nhost development secrets via unauthenticated cross-origin requests to the local config server.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-64cj-qvx5-m4f3, GO-2026-5166

## What is CVE-2026-47671?

CVE-2026-47671 is a medium-severity missing authorization vulnerability in nhost cli, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-47671?

3 open source packages ship an affected version, including github.com/nhost/nhost. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/nhost/nhost` | Go | All versions | 0.0.0-20260518172022-e407511627d2 |
| `github.com/nhost/nhost` | Go | All versions | 0.0.0-20260518172022-e407511627d2 |
| `github.com/nhost/nhost` | Go | All versions | 0.0.0-20260518172022-e407511627d2 |

Products: Nhost Cli.

## How do I fix CVE-2026-47671?

Upgrade github.com/nhost/nhost to 0.0.0-20260518172022-e407511627d2 or later.

## Is CVE-2026-47671 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47671 exists.

## Other vulnerabilities in nhost cli

- [CVE-2026-34200](https://insights.sbomify.com/CVE-2026-34200/): Nhost CLI MCP Server: Missing Inbound Authentication on Explicitly Bound Network Port (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47671 and fix it if it is affected.

What it is: CVE-2026-47671 is a medium-severity missing authorization vulnerability in nhost cli, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47671 exists.

Affected packages and fixed versions:
- github.com/nhost/nhost (Go): affected all versions; fixed in 0.0.0-20260518172022-e407511627d2
- github.com/nhost/nhost (Go): affected all versions; fixed in 0.0.0-20260518172022-e407511627d2
- github.com/nhost/nhost (Go): affected all versions; fixed in 0.0.0-20260518172022-e407511627d2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47671/ (Markdown: https://insights.sbomify.com/CVE-2026-47671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47671
- OSV: https://osv.dev/vulnerability/CVE-2026-47671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47671/
Summaries are generated and may contain mistakes; the official description above is the record.