LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some NATS Server deployments can leak client credentials through the monitoring interface. The issue only applies when credentials are supplied on the command line and the monitoring port is enabled. Anyone able to reach that monitoring endpoint could read the unredacted command-line arguments. Fixed versions are available.

Executive priority

Treat this as a prompt remediation item for infrastructure teams running NATS. Business risk is credential disclosure, which can enable unauthorized messaging access. Prioritize systems with reachable monitoring ports, then complete version upgrades and credential handling changes.

Technical view

CVE-2026-33247 affects nats-server before 2.11.15 and 2.12.0-RC.1 through before 2.12.6. The /debug/vars monitoring endpoint exposes argv without redaction, disclosing static client credentials passed via command-line arguments. CVSS 3.1 is 7.5, driven by unauthenticated network confidentiality impact.

Likely exposure

Highest exposure is internet-facing or broadly reachable NATS monitoring ports combined with credentials passed in argv. Deployments using configuration files for credentials, disabling monitoring, or limiting monitoring to trusted networks are less exposed. Evidence does not indicate all NATS deployments are vulnerable.

Exploitation context

The source bundle reports no KEV listing and provides no evidence of active exploitation. Exploitation requires network access to the monitoring endpoint and a deployment pattern where secrets are present in command-line arguments.

Researcher notes

The vulnerability is configuration-dependent: affected version plus argv secrets plus enabled monitoring. Mapped CWEs are CWE-214 and CWE-215. The sources name fixed upstream versions and workarounds but do not provide active exploitation evidence. Downstream Red Hat advisories are referenced for vendor-specific status.

Mitigation direction

  • Upgrade nats-server to 2.11.15, 2.12.6, or later fixed versions.
  • Move credentials from argv into a configuration file.
  • Disable the monitoring port when secrets are supplied via argv.
  • Restrict monitoring access to trusted networks only.
  • Review Red Hat errata if using Red Hat-packaged downstream products.
  • Rotate exposed credentials if monitoring data may have been accessible.

Validation and detection

  • Inventory nats-server versions and identify builds below the fixed releases.
  • Check whether credentials are passed as command-line arguments.
  • Confirm whether the monitoring port is enabled and who can reach it.
  • Review monitoring endpoint exposure for unredacted argv disclosure.
  • Assess logs and access records for unexpected monitoring access.
  • Verify credential rotation where exposure cannot be ruled out.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-214: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-215: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-33247 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-33247Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPgithub.com/nats-io/nats-server: NATS-Server: Information disclosure of credentials via monitoring port and command-line arguments
other:Red Hat severity ratingcvssV3_1
  • 2026-03-25T21:02:07.985Z: Reported to Red Hat.
  • 2026-03-25T20:02:18.868Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nats-ionats-server< 2.11.15, >= 2.12.0-RC.1, < 2.12.6Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-214 · source CWE mapping

Invocation of Process Using Visible Sensitive Information

Invocation of Process Using Visible Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-215 · source CWE mapping

Insertion of Sensitive Information Into Debugging Code

Insertion of Sensitive Information Into Debugging Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.