CVE-2026-58214: NATS Server MQTT subscribe permission bypass exposes internal QoS 2 metadata

Medium CVSS 4.3

OSV id
GHSA-4g68-3pwx-5vfj
Also known as
BIT-nats-2026-58214, CVE-2026-58214
Published
Last modified

Affected packages

PackageAffected versionsFixed in
github.com/nats-io/nats-server/v2
Go
< 2.12.12 2.12.12
github.com/nats-io/nats-server/v2
Go
>= 2.14.0-RC.1, < 2.14.3 2.14.3

How to fix it

github.com/nats-io/nats-server/v2 (Go)

Upgrade github.com/nats-io/nats-server/v2 to 2.12.12 or later.

go get github.com/nats-io/nats-server/v2@v2.12.12
go mod tidy
  • Indirect Go modules are upgraded the same way (`go get module@version`).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

github.com/nats-io/nats-server/v2 (Go)

Upgrade github.com/nats-io/nats-server/v2 to 2.14.3 or later.

go get github.com/nats-io/nats-server/v2@v2.14.3
go mod tidy
  • Indirect Go modules are upgraded the same way (`go get module@version`).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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 MQTT support uses internal $MQTT.* subjects to implement MQTT protocol features such as QoS handling.

Problem Description

An authenticated MQTT client could subscribe to an internal MQTT delivery subject that was not intended to be available to clients.

This bypassed configured subscribe permissions for that internal subject family and exposed MQTT QoS2 protocol metadata for sessions in the account. Message payloads were not exposed through this path.

This issue was related to an incomplete restriction on internal MQTT subjects. It affected MQTT users whose ordinary subscribe permissions would not otherwise allow access to those internal subjects.

Affected Versions

Versions v2.14.2, v2.12.7 and below are vulnerable. The issue is fixed in v2.14.3 and v2.12.8.

Workarounds

No known workaround for deployments that require MQTT. Upgrade to a fixed release. Deployments not using MQTT are not affected.

References

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.