Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

NATS: Message tracing can be redirected to arbitrary subject

CVSS 3.1 4.3 MEDIUMEUVD CVSS 3.1 4.3 CVSS 3.1 · [email protected] · Secondary 4.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/nats-io/nats-server/v2 2.11.15Fixed by github.com/nats-io/nats-server/v2 2.12.6osv · severity unknownFixed by github.com/nats-io/nats-server/v2 2.11.15Fixed by github.com/nats-io/nats-server/v2 2.12.6KEV status unknown

cve-program · CVE-2026-33249

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-16000

Published

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.

Read the publisher's advisory

nvd · CVE-2026-33249

Published

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.

Read the publisher's advisory

osv · GHSA-8m2x-3m6q-6w8j

Published

### 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 supports telemetry on messages, using the per-message NATS headers. ### Problem Description 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. ### Affected Versions Any version before v2.12.6 or v2.11.15 ### Workarounds None.

Read the publisher's advisory

osv · GO-2026-4826

Published

NATS: Message tracing can be redirected to arbitrary subject in github.com/nats-io/nats-server

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 12:11 UTC · 256 of 275 readable · 252 fully read · documentation 469/469 current