Review reviewHigh

CVE-2026-29785

nats-io nats-server, Multicluster Global Hub 1.5.4, Red Hat multicluster global hub 1.4.4

NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.14 and 2.12.5, if the nats-server has the "leafnode" configuration enabled (not default), then anyone who can connect can crash the nats-server by triggering a panic. This happens pre-authentication and requires that compression be enabled (which it is, by default, when leafnodes are used). Versions 2.11.14 and 2.12.5 contain a fix. As a workaround, disable compression on the leafnode port.

CVSS
7.5
EPSS
0.66%
48.0% percentile
CISA KEV
Not listed
Published
2026.03.26
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.66%
Technical severityCVSS 7.5

Vulnerability overview

NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.14 and 2.12.5, if the nats-server has the "leafnode" configuration enabled (not default), then anyone who can connect can crash the nats-server by triggering a panic. This happens pre-authentication and requires that compression be enabled (which it is, by default, when leafnodes are used). Versions 2.11.14 and 2.12.5 contain a fix. As a workaround, disable compression on the leafnode port.

Affected product and versions

Product
nats-io nats-server, Multicluster Global Hub 1.5.4, Red Hat multicluster global hub 1.4.4
Affected versions
>= < 2.11.14, >= >= 2.12.0-RC.1, < 2.12.5, < 2.11.14, >= 2.12.0 < 2.12.5
Fixed versions
2.11.14, 2.12.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that nats-io nats-server, Multicluster Global Hub 1.5.4, Red Hat multicluster global hub 1.4.4 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
CWE-409, CWE-476