BIT-nats-2026-33246

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/nats/BIT-nats-2026-33246.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-nats-2026-33246
Aliases
Published
2026-03-27T17:45:23.082Z
Modified
2026-03-27T18:26:07.658196Z
Summary
NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers
Details

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 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. Prior to versions 2.11.15 and 2.12.6, NATS clients relying upon the Nats-Request-Info: header could be spoofed. This 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. Versions 2.11.15 and 2.12.6 contain a fix. No known workarounds are available.

Database specific
{
    "cpes": [
        "cpe:2.3:a:nats:nats_server:*:*:*:*:*:go:*:*"
    ],
    "severity": "Medium"
}
References

Affected packages

Bitnami / nats

Package

Name
nats
Purl
pkg:bitnami/nats

Severity

  • 5.4 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.11.15
Introduced
2.12.0
Fixed
2.12.6

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/nats/BIT-nats-2026-33246.json"