NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2026-58214 — nats-server

MEDIUMFix: nats-io/nats-server@297b166

CVE-2026-58214 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in github.com/nats-io/nats-server/v2. A fix is available for github.com/nats-io/nats-server/v2 — see the affected versions and patch details below.

NATS Server: MQTT subscribe ACL bypass via $MQTT.deliver.pubrel prefix (incomplete fix for CVE-2026-33217)

Also known asBIT-nats-2026-58214GHSA-4g68-3pwx-5vfj
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-58214.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk
0.00%0.28%0.57%0.85%0.3%0.3%0.3%0.3%0.3%Aug 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/nats-io/nats-server/v2🐹github.com/nats-io/nats-server/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 uses internal $MQTT.* subjects to implement MQTT protocol features such as QoS handling.

Problem Description

An authenticated MQTT client could subscribe to an internal MQTT delivery subject that was not intended to be available to clients.

This bypassed configured subscribe permissions for that internal subject family and exposed MQTT QoS2 protocol metadata for sessions in the account. Message payloads were not exposed through this path.

This issue was related to an incomplete restriction on internal MQTT subjects. It affected MQTT users whose ordinary subscribe permissions would not otherwise allow access to those internal subjects.

Affected Versions

Versions v2.14.2, v2.12.7 and below are vulnerable. The issue is fixed in v2.14.3 and v2.12.8.

Workarounds

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

References

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/nats-io/nats-server/v2all versions2.12.12go get github.com/nats-io/nats-server/v2@v2.12.12
🐹Gogithub.com/nats-io/nats-server/v2≥ 2.14.0-RC.1&&< 2.14.32.14.3go get github.com/nats-io/nats-server/v2@v2.14.3

Affected Products

1 product · 2 configurations
Application
nats-serverlinuxfoundation
≥ 2.14.0 && < 2.14.3
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nats-io/nats-server/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/nats-io/nats-server/v2 to 2.12.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-58214 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat Hardened Imagesnats-server2-14-main-2.14.3-1.hum1RHSA-2026:36016
Red Hat Hardened Imagesnats-server2-12-main-2.12.12-1.hum1RHSA-2026:36017

Frequently Asked Questions

### 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 uses internal `$MQTT.*` subjects to implement MQTT protocol features such as QoS handling. ### Problem Description An authenticated MQTT client could subscribe to an internal MQTT delivery subject that was not intended to be available to clients. This bypassed configured subscribe permissions for that internal subject family and exposed MQTT QoS2 protocol metadata for sessions in the account. Message pa
O3 Security · Impact-Aware SCA

Is CVE-2026-58214 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2026-58214: nats-server — Fixed in 2.12.12