Nhost CLI local configserver allows cross-origin unauthenticated read/write access to local development configuration and secrets

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-47671: 0.35% estimated exploitation activity in the next 30 days; percentile 29.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details The CLI registers a hidden configserver command in cli/main.go:39 and cli/main.go:41. That command is used as the local development configserver image in nhost dev: cli/cmd/dev/up.go:176 through cli/cmd/dev/up.go:200 select nhost/cli:<version as the configserver image, and cli/dockercompose/configserver.go:80…

Published by the source

4 Jun 2026, 17:43 UTC

Last modified by the source

4 Jun 2026, 17:43 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-64cj-qvx5-m4f3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47671

Advisory: Nhost CLI local configserver allows cross-origin unauthenticated read/write access to local development configuration and secrets
IDs: CVE-2026-47671, GHSA-64cj-qvx5-m4f3
Record: https://patchnext.com/advisories/cve-2026-47671 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/nhost/nhost 0.0.0-20260518172022-e407511627d2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nhost/nhost: affected < 0.0.0-20260518172022-e407511627d2; fixed in 0.0.0-20260518172022-e407511627d2

## Suggested inspection (read-only)
- Go github.com/nhost/nhost: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/nhost/nhost.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-64cj-qvx5-m4f3 (GitHub-reviewed advisory GHSA-64cj-qvx5-m4f3 lists affected ranges: Go github.com/nhost/nhost >=0 <0.0.0-20260518172022-e407511627d2)

Commands are suggestions: review each one before running it.