CVE-2026-33246: NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers
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 allows hub/spoke topologies using "leafnode" connections by other nats-servers. NATS messages can have headers. Problem Description The nats-server offers a Nats-Request-Info: message header, providing information about a request.
Published Mar 24, 2026 · Updated Mar 27, 2026
Affected packages
github.com/nats-io/nats-server/v2
- Ecosystem
- Go
- Affected
- < 2.11.15
- Fixed in
- 2.11.15
- Check
go list -m github.com/nats-io/nats-server/v2
github.com/nats-io/nats-server/v2
- Ecosystem
- Go
- Affected
- >= 2.12.0-RC.1, < 2.12.6
- Fixed in
- 2.12.6
- Check
go list -m github.com/nats-io/nats-server/v2
github.com/nats-io/nats-server
- Ecosystem
- Go
- Affected
- > 0
- Fixed in
- No patched version yet
- Check
go list -m github.com/nats-io/nats-server
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 allows hub/spoke topologies using "leafnode" connections by other nats-servers. NATS messages can have headers.
Problem Description
The nats-server offers a Nats-Request-Info: message header, providing information about a request. This is supposed to provide enough information to allow for account/user identification, such that NATS clients could make their own decisions on how to trust a message, provided that they trust the nats-server as a broker.
A leafnode connecting to a nats-server is not fully trusted unless the system account is bridged too. Thus identity claims should not have propagated unchecked.
Thus NATS clients relying upon the Nats-Request-Info: header could be spoofed.
Does not directly affect the nats-server itself, but the CVSS Confidentiality and Integrity scores are based upon what a hypothetical client might choose to do with this NATS header.
Affected Versions
Any version before v2.12.6 or v2.11.15
Workarounds
None.
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 entriesCVE-2026-58208
NATS Server: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled
medium6.8Nov 20, 2026CVE-2026-58209
NATS Server MQTT retained messages and QoS replay bypass subscription deny rules
medium4.3Nov 20, 2026CVE-2026-58210
NATS Server allows unauthenticated memory exhaustion through incomplete MQTT CONNECT packets
high7.5Nov 20, 2026CVE-2026-58254
nats-server Leaf node connections bypass Nats-Trace-Dest permission check
medium6.5Nov 20, 2026CVE-2026-58213
NATS Server: MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection
high7.1Nov 19, 2026CVE-2026-58214
NATS Server MQTT subscribe permission bypass exposes internal QoS 2 metadata
medium4.3Nov 19, 2026
