Advisory record · GHSA-x6g4-f6q3-fqvv

NATS credentials are exposed in monitoring port via command-line argv

CVSS 7.4 HighEPSS 0.0043 · 37th percentile

Published by the GitHub Advisory Database at 24 Mar 2026, 20:44 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nats-io/nats-server/v2Go<2.11.15 || >=2.12.0-RC.1, <2.12.62.11.15, 2.12.6
Identifiers
GHSA-x6g4-f6q3-fqvv · BIT-nats-2026-33247 · CVE-2026-33247 · GO-2026-4827
Weakness (CWE)
CWE-214 · CWE-215
Published
24 Mar 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The nats-server Go package, versions before 2.11.15 and from 2.12.0-RC.1 before 2.12.6, exposes its static client credentials when they are passed on the command line and the monitoring port is enabled. Anyone who can reach the monitoring port's /debug/vars endpoint can read the unredacted command-line arguments, including those credentials. Upgrade to 2.11.15 or 2.12.6. Otherwise, move credentials into a configuration file and do not enable the monitoring port when secrets are passed via argv.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0043, the 37th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.