CVE-2026-58209

CVE-2026-58209 is a medium-severity incorrect authorization vulnerability in github.com/nats-io/nats-server/v2 (go), affecting versions < 2.12.12. It is fixed in 2.12.12, 2.14.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

NATS Server MQTT retained messages and QoS replay bypass subscription deny rules

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 MQTT support includes retained messages and QoS1+ durable delivery. NATS subscription permissions can allow broad wildcard subscriptions while denying more sensitive subjects.

Problem Description

MQTT retained message delivery and QoS1+ durable replay could deliver messages whose original topics matched a subscriber's configured subscribe deny rules.

Normal live delivery applied the delivery-time deny check. These MQTT delivery paths did not consistently recheck the concrete original topic before sending the MQTT PUBLISH to the subscriber.

The issue affects MQTT subscribers with broad wildcard subscribe permissions where more specific topics are denied. Normal live delivery can be blocked while retained or replayed delivery still sends the denied topic.

Affected Versions

Versions v2.14.2, v2.12.11 and below are vulnerable. The issue is fixed in v2.14.3 and v2.12.12.

Workarounds

No known workaround for deployments that require MQTT. Upgrade to a fixed release. Deployments not using MQTT are not affected.

References

Impact

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-58209 has a CVSS score of 4.3 (Medium). 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.12.12, 2.14.3); upgrading removes the vulnerable code path.

Affected versions

github.com/nats-io/nats-server/v2 (< 2.12.12) github.com/nats-io/nats-server/v2 (>= 2.14.0-RC.1, < 2.14.3)

Security releases

github.com/nats-io/nats-server/v2 → 2.12.12 (go) github.com/nats-io/nats-server/v2 → 2.14.3 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

github.com/nats-io/nats-server/v2 to 2.12.12 or later; github.com/nats-io/nats-server/v2 to 2.14.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-58209? CVE-2026-58209 is a medium-severity incorrect authorization vulnerability in github.com/nats-io/nats-server/v2 (go), affecting versions < 2.12.12. It is fixed in 2.12.12, 2.14.3. 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-58209? CVE-2026-58209 has a CVSS score of 4.3 (Medium). 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 versions of github.com/nats-io/nats-server/v2 are affected by CVE-2026-58209? github.com/nats-io/nats-server/v2 (go) versions < 2.12.12 is affected.
  4. Is there a fix for CVE-2026-58209? Yes. CVE-2026-58209 is fixed in 2.12.12, 2.14.3. Upgrade to this version or later.
  5. Is CVE-2026-58209 exploitable, and should I be worried? Whether CVE-2026-58209 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-58209 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-58209?
    • Upgrade github.com/nats-io/nats-server/v2 to 2.12.12 or later
    • Upgrade github.com/nats-io/nats-server/v2 to 2.14.3 or later

Other vulnerabilities in github.com/nats-io/nats-server/v2

Stop the waste.
Protect your environment with Kodem.