NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦 Bitnami
Not in CISA KEV

NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injectionGHSA-qrcv-3558-gj4f

Fix: nats-io/nats-server@366837c

GHSA-qrcv-3558-gj4f is a CWE-74 vulnerability in nats. A fix is available for nats — see the affected versions and patch details below.

Also known asCVE-2026-58213
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 18, 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 GHSA-qrcv-3558-gj4f.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk
0.00%0.31%0.63%0.94%0.3%0.4%0.4%0.4%0.4%Aug 26Oct 26Nov 26

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

Real-World Exposure

1 pkg affected
📦nats

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

Description

NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.1 and 2.12.9, an MQTT client could include protocol control characters in subscription filters that were later forwarded as NATS protocol data to route or leafnode connections, corrupting the forwarded protocol stream and allowing injection of unintended NATS protocol operations. This issue is fixed in versions 2.14.1 and 2.12.9.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦Bitnaminats≥ 2.14.0&&< 2.12.92.12.9

Affected Products

1 product · 2 configurations
Application
nats-serverlinuxfoundation
≥ 2.14.0 && < 2.14.1
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 nats, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update nats to 2.12.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrcv-3558-gj4f is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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 HatImportant
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

NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.1 and 2.12.9, an MQTT client could include protocol control characters in subscription filters that were later forwarded as NATS protocol data to route or leafnode connections, corrupting the forwarded protocol stream and allowing injection of unintended NATS protocol operations. This issue is fixed in versions 2.14.1 and 2.12.9.
O3 Security · Impact-Aware SCA

Is GHSA-qrcv-3558-gj4f in your dependencies?

Find it across Bitnami, including transitive dependencies.

NATS Server: MQTT SUBSCRIBE Protocol Injection via…