github.com/nats-io/nats-server/v2
Affected
- introduced
0, fixed2.11.15(semver)
Fixed versions
2.11.15
Fix
- Fixed version
2.11.15go get github.com/nats-io/nats-server/[email protected]
Advisory
Also known as: BIT-nats-2026-33248, CVE-2026-33248, GO-2026-4828
NATS has mTLS verify_and_map authentication bypass via incorrect Subject DN matching
Background
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.
One authentication model supported is mTLS, deriving the NATS client identity from properties of the TLS Client Certificate.
Problem Description
When using mTLS for client identity, with verify_and_map to derive a NATS identity from the client certificate's Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass.
This does require a valid certificate from a CA already trusted for client certificates, and DN naming patterns which the NATS maintainers consider highly unlikely.
So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their DN construction patterns might conceivably be impacted.
Affected Versions
Fixed in nats-server 2.12.6 & 2.11.15
Workarounds
Developers should review their CA issuing practices.
Medium Basis: The source's own band: MODERATE
0, fixed 2.11.15 (semver)2.11.15
2.11.15go get github.com/nats-io/nats-server/[email protected]2.12.0-RC.1, fixed 2.12.6 (semver)2.12.6
2.12.6go get github.com/nats-io/nats-server/[email protected]0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0