Skip to main content
VulnerabilityPublished

CVE-2026-58250: nats-server · NULL Pointer Dereference

Affects nats-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.12.8 or 2.11.17 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.12.8, 2.11.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade nats-server and nats-io/nats-server to 2.12.8 or 2.11.17.

Affected software

ProductAffectedFixed in
nats-ionats-serverAffected
  • >=2.12.0-preview.1 <2.12.8
Fixed in
  • 2.12.8
nats-ionats-serverAffected
  • <2.11.17
Fixed in
  • 2.11.17
GitHubnats-io/nats-serverpkg:github/nats-io/nats-serverOther threatsAffected
  • <2.11.17
  • <2.12.8
Fixed in
  • 2.11.17
  • 2.12.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade nats-server to version 2.12.8 or 2.11.17 or later where the vulnerability is fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory stating the fix is included in these versions.

Description

NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.12.8 and 2.11.17, an unauthenticated peer with network access to a leafnode listener with compression enabled could crash the server during the pre-authentication leafnode handshake by sending repeated leafnode INFO protocol messages before authentication and account setup completed. This issue is fixed in versions 2.12.8 and 2.11.17.

References

Community reviews

Loading reviews…