CVE-2026-33249

unknown

Published 2026-03-24 · Modified 2026-03-30

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

Description

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 sent to an arbitrary valid subject, including those to which the client does not have publish permission. The payload is a valid trace message and not chosen by the attacker. Versions 2.11.15 and 2.12.6 contain a fix. No known workarounds are available.

Predictions

Exploit likelihood

30%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OS	Version	Status	Fixed in
sles		affected
debian	bookworm	fixed	`0`
debian	forky	fixed	`2.12.6-1`
debian	sid	fixed	`2.12.6-1`
debian	trixie	fixed	`0`

Package impact

Ecosystem	Package	Vulnerable	Fixed
Go	github.com/nats-io/nats-server/v2	`>=2.11.0,<2.11.15`	`2.11.15`
Go	github.com/nats-io/nats-server/v2	`>=2.12.0-preview.1,<2.12.6`	`2.12.6`
Go	github.com/nats-io/nats-server

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.