CVE-2026-33247: CWE-215: Insertion of Sensitive Information Into Debugging Code in nats-io nats-server
NATS-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.
AI Analysis
Technical Summary
NATS-Server versions prior to 2.11.15 and 2.12.6 contain a vulnerability where static credentials passed via command-line arguments are exposed in plaintext through the /debug/vars endpoint on the monitoring port if it is enabled. This endpoint reveals an unredacted copy of the command-line arguments, allowing an attacker with network access to the monitoring port to obtain sensitive authentication credentials. The issue is classified under CWE-215 (Insertion of Sensitive Information Into Debugging Code) and CWE-214 (Information Exposure Through Debug Information). The vulnerability has a CVSS v3.1 base score of 7.4 (high severity) with network attack vector, low attack complexity, no privileges required, and high confidentiality impact. The vendor has released fixed versions 2.11.15 and 2.12.6 that address this issue. Workarounds include avoiding passing credentials via argv and disabling the monitoring port if credentials are passed this way. The vendor advisory notes that mitigation options are limited and recommends upgrading to fixed versions.
Potential Impact
An attacker with network access to the monitoring port can retrieve sensitive static credentials passed via command-line arguments, leading to a high confidentiality impact. This exposure can compromise authentication security for the nats-server instance. There is no impact on integrity or availability reported. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in nats-server versions 2.11.15 and 2.12.6. Users should upgrade to these or later versions to remediate the vulnerability. As a workaround, avoid passing static credentials via command-line arguments and instead configure them in a configuration file. Additionally, do not enable the monitoring port if credentials are passed via argv. Restrict access to the monitoring port to trusted network sources only. The vendor advisory indicates that mitigation options other than upgrading may not meet criteria for ease of use or stability.
CVE-2026-33247: CWE-215: Insertion of Sensitive Information Into Debugging Code in nats-io nats-server
Description
NATS-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.
CVSS v3.1
Score 7.4high
Affected software
pkg:github/nats-io/nats-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
NATS-Server versions prior to 2.11.15 and 2.12.6 contain a vulnerability where static credentials passed via command-line arguments are exposed in plaintext through the /debug/vars endpoint on the monitoring port if it is enabled. This endpoint reveals an unredacted copy of the command-line arguments, allowing an attacker with network access to the monitoring port to obtain sensitive authentication credentials. The issue is classified under CWE-215 (Insertion of Sensitive Information Into Debugging Code) and CWE-214 (Information Exposure Through Debug Information). The vulnerability has a CVSS v3.1 base score of 7.4 (high severity) with network attack vector, low attack complexity, no privileges required, and high confidentiality impact. The vendor has released fixed versions 2.11.15 and 2.12.6 that address this issue. Workarounds include avoiding passing credentials via argv and disabling the monitoring port if credentials are passed this way. The vendor advisory notes that mitigation options are limited and recommends upgrading to fixed versions.
Potential Impact
An attacker with network access to the monitoring port can retrieve sensitive static credentials passed via command-line arguments, leading to a high confidentiality impact. This exposure can compromise authentication security for the nats-server instance. There is no impact on integrity or availability reported. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in nats-server versions 2.11.15 and 2.12.6. Users should upgrade to these or later versions to remediate the vulnerability. As a workaround, avoid passing static credentials via command-line arguments and instead configure them in a configuration file. Additionally, do not enable the monitoring port if credentials are passed via argv. Restrict access to the monitoring port to trusted network sources only. The vendor advisory indicates that mitigation options other than upgrading may not meet criteria for ease of use or stability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-18T02:42:27.509Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-33247","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22347","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:21769","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:23345","vendor":"Red Hat"}]
Threat ID: 69c4427ef4197a8e3b7e9796
Added to database: 03/25/2026, 20:15:58 UTC
Last enriched: 08/06/2026, 16:13:01 UTC
Last updated: 08/12/2026, 00:41:11 UTC
Views: 154
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.