CVE-2026-33216: NATS has MQTT plaintext password disclosure
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, for MQTT deployments using usercodes/passwords: MQTT passwords are incorrectly classified as a non-authenticating identity statement (JWT) and exposed via monitoring endpoints. Versions 2.11.14 and 2.12.6 contain a fix. As a workaround, ensure monitoring end-points are adequately secured. Best practice remains to not expose the monitoring endpoint to the Internet or other untrusted network users.
Security readout for executives and security teams
Plain-English summary
Affected NATS servers can reveal MQTT user passwords through monitoring endpoints. An attacker who can reach those endpoints may obtain credentials without authenticating, creating a serious confidentiality and account-compromise risk. Exposure requires MQTT username/password authentication and accessible monitoring endpoints.
Executive priority
Treat as urgent where MQTT password authentication and exposed monitoring coexist. Prioritize immediate endpoint isolation, then upgrade and credential rotation. Lower priority may be justified only after confirming monitoring is inaccessible to untrusted users or the affected MQTT configuration is absent.
Technical view
NATS incorrectly treats MQTT passwords as non-authenticating JWT identity data, causing plaintext passwords to appear in monitoring output. The stated affected ranges are below 2.11.15 and 2.12.0-RC.1 through 2.12.5. CVSS 3.1 is 8.6, reflecting unauthenticated network access and high confidentiality impact without direct integrity or availability impact.
Likely exposure
Highest risk applies to affected NATS versions using MQTT usercodes/passwords where monitoring endpoints are reachable from the Internet or untrusted networks. Deployments not using MQTT password authentication, or with monitoring strictly restricted to trusted administrators, have substantially lower exposure to this flaw.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Exploitation would require network access to an affected monitoring endpoint; no prior privileges or user interaction are indicated by the CVSS vector.
Researcher notes
The source bundle is internally inconsistent: its affected range includes 2.11.14, while its description also calls 2.11.14 fixed. Confirm the correct 2.11 remediation release with the NATS advisory. The evidence supports credential disclosure, but not demonstrated credential reuse, downstream compromise, or active exploitation.
Mitigation direction
Upgrade to a release outside the stated affected ranges, subject to vendor confirmation.
Use 2.12.6 or later for the 2.12 branch.
Restrict monitoring endpoints to trusted administrative networks and authenticated operators.
Rotate exposed MQTT passwords if monitoring access by untrusted parties cannot be ruled out.
Review the NATS advisory before selecting a 2.11 branch target because the supplied version statements conflict.
Validation and detection
Inventory NATS versions and identify deployments using MQTT username/password authentication.
Confirm monitoring endpoints are not reachable from the Internet or untrusted network segments.
Review monitoring access logs for unexpected clients during the vulnerable period.
Verify upgraded instances report a vendor-confirmed unaffected version.
Check monitoring responses safely to confirm MQTT passwords are no longer disclosed.
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-213: 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.
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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-213 · source CWE mapping
Exposure of Sensitive Information Due to Incompatible Policies
Exposure of Sensitive Information Due to Incompatible Policies represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Plaintext Storage of a Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.