NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

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

highCVSS 3.1 7.1GHSA-qrcv-3558-gj4f

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.

Published Nov 19, 2026

Affected packages

github.com/nats-io/nats-server/v2

Ecosystem
Go
Affected
< 2.12.9
Fixed in
2.12.9
Check
go list -m github.com/nats-io/nats-server/v2

github.com/nats-io/nats-server/v2

Ecosystem
Go
Affected
>= 2.14.0-RC.1, < 2.14.1
Fixed in
2.14.1
Check
go list -m github.com/nats-io/nats-server/v2

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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:
  • Credit: @thesecguy45

Credited to thesecguy45.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries