CVE-2026-33217

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 MQTT client interface.

Problem Description

When using ACLs on message subjects, these ACLs were not applied in the $MQTT.> namespace, allowing MQTT clients to bypass ACL checks for MQTT subjects.

Affected Versions

Any version before v2.12.6 or v2.11.15

Workarounds

None.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-33217 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.11.15, 2.12.6); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-33217? CVE-2026-33217 is a high-severity incorrect authorization vulnerability in github.com/nats-io/nats-server/v2 (go), affecting versions < 2.11.15. It is fixed in 2.11.15, 2.12.6. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-33217? CVE-2026-33217 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-33217?
   • github.com/nats-io/nats-server/v2 (go) (versions < 2.11.15)
   • github.com/nats-io/nats-server (go) (versions > 0)
4. Is there a fix for CVE-2026-33217? Yes. CVE-2026-33217 is fixed in 2.11.15, 2.12.6. Upgrade to this version or later.
5. Is CVE-2026-33217 exploitable, and should I be worried? Whether CVE-2026-33217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33217 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33217?
   • Upgrade github.com/nats-io/nats-server/v2 to 2.11.15 or later
   • Upgrade github.com/nats-io/nats-server/v2 to 2.12.6 or later