CVE-2026-33215: GO-2026-4833 - NATS is vulnerable to MQTT hijacking via Client ID in github.com/nats-io/nats-server

CVE-2026-33215 · Severity: low · CVSS 3.1 · Published 2026-03-26

NATS is vulnerable to MQTT hijacking via Client ID in github.com/nats-io/nats-server

Technologies: github.com/nats-io/nats-server (Go), github.com/nats-io/nats-server/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2026-33215 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33215 being exploited in the wild.
How severe is CVE-2026-33215?
Low severity, with a CVSS score of 3.1, published 26 March 2026.
Which products and versions are affected?
github.com/nats-io/nats-server (Go) SEMVER:introduced=0; github.com/nats-io/nats-server/v2 (Go) SEMVER:introduced=0,fixed=2.11.15, SEMVER:introduced=0,fixed=2.11.15,introduced=2.12.0-RC.1,fixed=2.12.6.
Is there a fix for CVE-2026-33215?
Yes. github.com/nats-io/nats-server/v2 (Go): upgrade to 2.11.15, 2.12.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33215?
Check whether you run github.com/nats-io/nats-server (Go) or github.com/nats-io/nats-server/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/nats-io/nats-server/v2 (Go): upgrade to 2.11.15, 2.12.6 or later
    go get github.com/nats-io/nats-server/v2@v2.12.6

Affected products

  • github.com/nats-io/nats-server (Go) SEMVER:introduced=0
  • github.com/nats-io/nats-server/v2 (Go) SEMVER:introduced=0,fixed=2.11.15, SEMVER:introduced=0,fixed=2.11.15,introduced=2.12.0-RC.1,fixed=2.12.6

Identifiers

  • CVE-2026-33215
  • GHSA-fcjp-h8cc-6879
  • GO-2026-4833

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.