HighGHSA-qrcv-3558-gj4fBIT-nats-2026-58213CVE-2026-58213

NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection

Published 19 Nov 2026 · Updated 19 Nov 2026

Is your project on an affected github.com/nats-io/nats-server/v2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<2.12.9
Fixed in
2.12.9
Update to the fixed version for your release line, for example:go get github.com/nats-io/nats-server/v2@v2.12.9
Affected
>=2.14.0-RC.1 <2.14.1
Fixed in
2.14.1
Update to the fixed version for your release line, for example:go get github.com/nats-io/nats-server/v2@v2.14.1

Details

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 supports MQTT clients and can bridge MQTT activity into NATS subjects across routes and leafnode connections.

Problem Description

An MQTT client could include protocol control characters in subscription filters that were later forwarded as NATS protocol data to route or leafnode connections.

This could corrupt the forwarded protocol stream and allow injection of unintended NATS protocol operations, potentially across cluster nodes or accounts where route or gateway connections are present.

Anonymous MQTT deployments are higher risk because no credentials are required to reach the affected parser. Authenticated deployments are still affected for clients allowed to create MQTT subscriptions.

Affected Versions

Versions v2.14.0, v2.12.8 and below are vulnerable. The issue is fixed in v2.14.1 and v2.12.9.

Workarounds

Disable anonymous MQTT access where it is not required. Deployments that need MQTT have no known complete workaround other than upgrading.

References

  • GHSA advisory: <https://github.com/nats-io/nats-server/security/advisories/GHSA-qrcv-3558-gj4f>
  • Credit: @thesecguy45

Is GHSA-qrcv-3558-gj4f in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/nats-io/nats-server/v2, and gives you the command that fixes it.

More advisories for github.com/nats-io/nats-server/v2

  • MediumCVE-2026-58208NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled · 20 Nov 2026
  • HighCVE-2026-58210NATS Server allows unauthenticated memory exhaustion through incomplete MQTT CONNECT packets · 20 Nov 2026
  • MediumCVE-2026-58209NATS Server MQTT retained messages and QoS replay bypass subscription deny rules · 20 Nov 2026
  • MediumCVE-2026-58214NATS Server MQTT subscribe permission bypass exposes internal QoS 2 metadata · 19 Nov 2026
  • LowCVE-2026-29785NATS Server panic via malicious compression on leafnode port in github.com/nats-io/nats-server · 26 Mar 2026
  • LowCVE-2026-33246NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers in github.com/nats-io/nats-server · 26 Mar 2026
All 56 advisories for github.com/nats-io/nats-server/v2

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.