NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-33247: NATS credentials are exposed in monitoring port via command-line argv

highCVSS 3.1 7.4GHSA-x6g4-f6q3-fqvv

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.

Published Mar 24, 2026 · Updated Mar 27, 2026

Affected packages

github.com/nats-io/nats-server/v2

Ecosystem
Go
Affected
< 2.11.15
Fixed in
2.11.15
Check
go list -m github.com/nats-io/nats-server/v2

github.com/nats-io/nats-server/v2

Ecosystem
Go
Affected
>= 2.12.0-RC.1, < 2.12.6
Fixed in
2.12.6
Check
go list -m github.com/nats-io/nats-server/v2

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries