Summary
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in NATS Server ausnutzen, um Informationen offenzulegen oder zu manipulieren, einen Denial-of-Service zu verursachen und Sicherheitsmechanismen zu umgehen.
Product
Der NATS-Server ist ein Server für NATS.io, das Cloud- und Edge-native Messaging-System.
Vulnerabilities 11
-
High 8.6
NATS has MQTT plaintext password disclosure
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, for MQTT deployments using usercodes/passwords: MQTT passwords are incorrectly classified as a non-authenticating identity st…
-
High 7.5
NATS has pre-auth server panic via leafnode handling
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, a client which can connect to the leafnode port can crash the nats-server with a certain malformed message pre-authentication…
-
High 7.4
NATS credentials are exposed in monitoring port via command-line argv
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, if a nats-server is run with static credentials for all clients provided via argv (the command-line), then those credentials …
-
High 7.1
NATS allows MQTT clients to bypass ACL checks
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using ACLs on message subjects, these ACLs were not applied in the `$MQTT.>` namespace, allowing MQTT clients to bypass …
-
Medium 6.5
NATS is vulnerable to MQTT hijacking via Client ID
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. The nats-server provides an MQTT client interface. Prior to versions 2.11.15 and 2.12.5, Sessions and Messages can by hijacked via MQTT Client ID malfeasance. Vers…
-
Medium 6.4
NATS Server: Incomplete Stripping of Nats-Request-Info Header Allows Identity Spoofing
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, the NATS message header `Nats-Request-Info:` is supposed to be a guarantee of identity by the NATS server, but the stripping …
-
Medium 6.4
NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. 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 ac…
-
Medium 5.3
NATS is vulnerable to pre-auth DoS through WebSockets client service
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, a malicious client which can connect to the WebSockets port can cause unbounded memory use in the nats-server before authenti…
-
Medium 4.9
NATS JetStream has an authorization bypass through its Management API
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, users with JetStream admin API access to restore one stream could restore to other stream names, impacting data which should …
-
Medium 4.3
NATS: Message tracing can be redirected to arbitrary subject
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Starting in version 2.11.0 and prior to versions 2.11.15 and 2.12.6, a valid client which uses message tracing headers can indicate that the trace messages can be …
-
Medium 4.2
NATS has mTLS verify_and_map authentication bypass via incorrect Subject DN matching
NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate's Subject DN…
Revision history
-
#3
Neue Updates von Red Hat aufgenommen
-
#2
Referenz(en) aufgenommen: EUVD-2026-15973, EUVD-2026-15970, EUVD-2026-15968, EUVD-2026-15964, EUVD-2026-15975, EUVD-2026-15994, EUVD-2026-15996, EUVD-2026-15999, EUVD-2026-16000, EUVD-2026-15966
-
#1
Initiale Fassung
References
-
NATS Security Advisory 2026-05 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-05.txt
-
NATS Security Advisory 2026-06 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-06.txt
-
NATS Security Advisory 2026-07 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-07.txt
-
NATS Security Advisory 2026-08 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-08.txt
-
NATS Security Advisory 2026-09 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-09.txt
-
NATS Security Advisory 2026-10 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-10.txt
-
NATS Security Advisory 2026-11 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-11.txt
-
NATS Security Advisory 2026-12 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-12.txt
-
NATS Security Advisory 2026-13 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-13.txt
-
NATS Security Advisory 2026-14 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-14.txt
-
NATS Security Advisory 2026-15 vom 2026-03-24
https://advisories.nats.io/CVE/secnote-2026-15.txt
-
Red Hat Security Advisory RHSA-2026:22347 vom 2026-06-02
https://access.redhat.com/errata/RHSA-2026:22347