NATS credentials are exposed in monitoring port via command-line argv
cve-program · CVE-2026-33247
PublishedNATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, if a nats-server is run with static credentials for all clients provided via argv (the command-line), then those credentials are visible to any user who can see the monitoring port, if that too is enabled. The `/debug/vars` end-point contains an unredacted copy of argv. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, configure credentials inside a configuration file instead of via argv, and do not enable the monitoring port if using secrets in argv. Best practice remains to not expose the monitoring port to the Internet, or to untrusted network sources.
Read the publisher's advisoryeuvd · EUVD-2026-15975
PublishedNATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, if a nats-server is run with static credentials for all clients provided via argv (the command-line), then those credentials are visible to any user who can see the monitoring port, if that too is enabled. The `/debug/vars` end-point contains an unredacted copy of argv. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, configure credentials inside a configuration file instead of via argv, and do not enable the monitoring port if using secrets in argv. Best practice remains to not expose the monitoring port to the Internet, or to untrusted network sources.
Read the publisher's advisorynvd · CVE-2026-33247
PublishedNATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, if a nats-server is run with static credentials for all clients provided via argv (the command-line), then those credentials are visible to any user who can see the monitoring port, if that too is enabled. The `/debug/vars` end-point contains an unredacted copy of argv. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, configure credentials inside a configuration file instead of via argv, and do not enable the monitoring port if using secrets in argv. Best practice remains to not expose the monitoring port to the Internet, or to untrusted network sources.
Read the publisher's advisoryosv · GHSA-x6g4-f6q3-fqvv
Published### Background NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing. The nats-server provides an optional monitoring port, which provides access to sensitive data. The nats-server can take certain configuration options on the command-line instead of requiring a configuration file. ### Problem Description If a nats-server is run with static credentials for all clients provided via argv (the command-line), then those credentials are visible to any user who can see the monitoring port, if that too is enabled. The `/debug/vars` end-point contains an unredacted copy of argv. ### Patches Fixed in nats-server 2.12.6 & 2.11.15 ### Workarounds The NATS Maintainers are bemused at the concept of someone deploying a real configuration using `--pass` to avoid a config file, but also enabling monitoring. Configure credentials inside a configuration file instead of via argv. Do not enable the monitoring port if using secrets in argv. Best practice remains to not expose the monitoring port to the Internet, or to untrusted network sources.
Read the publisher's advisoryosv · GO-2026-4827
PublishedNATS credentials are exposed in monitoring port via command-line argv in github.com/nats-io/nats-server
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-33247 · CVE overview and exploitation status
cve-program · CVE-2026-33247
- https://github.com/nats-io/nats-server/security/advisories/GHSA-x6g4-f6q3-fqvv
- https://advisories.nats.io/CVE/secnote-2026-14.txt
euvd · EUVD-2026-15975
- https://github.com/nats-io/nats-server/security/advisories/GHSA-x6g4-f6q3-fqvv
- https://advisories.nats.io/CVE/secnote-2026-14.txt
nvd · CVE-2026-33247
- https://advisories.nats.io/CVE/secnote-2026-14.txt
- https://github.com/nats-io/nats-server/security/advisories/GHSA-x6g4-f6q3-fqvv
- https://access.redhat.com/errata/RHSA-2026:21769
- https://access.redhat.com/errata/RHSA-2026:22347
- https://access.redhat.com/errata/RHSA-2026:23345
- https://access.redhat.com/security/cve/CVE-2026-33247
- https://bugzilla.redhat.com/show_bug.cgi?id=2451486
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33247.json
osv · GHSA-x6g4-f6q3-fqvv
- https://github.com/nats-io/nats-server/security/advisories/GHSA-x6g4-f6q3-fqvv
- https://nvd.nist.gov/vuln/detail/CVE-2026-33247
- https://advisories.nats.io/CVE/secnote-2026-14.txt
- https://github.com/nats-io/nats-server
- https://pkg.go.dev/vuln/GO-2026-4827
osv · GO-2026-4827
Related changes
Linked by CVE identifierNo related changes are available here.