Security readout for executives and security teams
Plain-English summary
Affected NATS servers may let a permitted MQTT client evade subject-level access rules and read or publish messages it should not access. This can expose confidential messaging data or allow unauthorized message changes. The issue affects specified releases before 2.11.15 and 2.12.6; upgrading is the only named remediation.
Executive priority
Treat this as a high-priority authorization failure. Expedite upgrades for internet-facing, multi-tenant, or sensitive MQTT messaging environments. Schedule prompt remediation elsewhere after confirming exposure. The expected business impact is unauthorized disclosure or alteration of messages; the supplied CVSS assessment does not indicate an availability impact.
Technical view
NATS subject ACL enforcement did not cover the `$MQTT.>` namespace, enabling MQTT clients to bypass ACL checks for MQTT subjects. Affected versions are below 2.11.15 and 2.12.0-RC.1 through 2.12.5. CVSS 3.1 is 8.1: network-accessible, low complexity, low privileges, no user interaction, with high confidentiality and integrity impact.
Likely exposure
Exposure requires an affected NATS server using MQTT and relying on subject ACLs for authorization. Risk increases where untrusted or lower-privileged MQTT clients can reach the service and sensitive subjects share the deployment. Servers without MQTT use are not shown by the supplied evidence to be exploitable through this flaw.
Exploitation context
The supplied sources do not report known active exploitation, and the CVE is not identified as being in KEV. The scoring indicates remote, low-complexity exploitation by a client with low privileges, without user interaction. This is an authorization bypass, not an unauthenticated server compromise according to the provided evidence.
Researcher notes
The issue maps to CWE-425 and CWE-863 and concerns missing authorization enforcement within a protocol-specific namespace. Assessment should distinguish native NATS traffic from MQTT traffic and verify whether subject ACLs form a security boundary. The supplied evidence identifies no workaround or public exploitation, so testing should remain defensive and avoid assuming broader server compromise.
Mitigation direction
- Upgrade the 2.11 branch to NATS Server 2.11.15 or later.
- Upgrade the 2.12 branch to NATS Server 2.12.6 or later.
- Prioritize MQTT-enabled deployments that use subject ACLs.
- Restrict MQTT service access until upgrades are complete where operationally feasible.
- Do not rely on a workaround; the advisory states none are known.
Validation and detection
- Inventory NATS Server versions across production, staging, edge, and embedded deployments.
- Identify instances with MQTT enabled and reachable by lower-privileged clients.
- Confirm upgraded instances report version 2.11.15, 2.12.6, or later.
- Review MQTT subject permissions and investigate unexpected access involving the `$MQTT.>` namespace.
- Retest authorized and unauthorized MQTT subject access after upgrading.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-425: 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 lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2026-33217 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2redhat-SADPCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N2.84.2GitHub_MVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-25T20:01:47.815Z: Reported to Red Hat.
- 2026-03-25T19:43:40.969Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/nats-io/nats-server/security/advisories/GHSA-jxxm-27vp-c3m5CVE reference, GitHub_M · x_refsource_CONFIRM
- https://advisories.nats.io/CVE/secnote-2026-07.txtCVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-33217CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2451446CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33217.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:22347CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:23345CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:21769CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Direct Request ('Forced Browsing')
Direct Request ('Forced Browsing') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.