CVE-2026-29785

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.0%
EPSS %ILE
60th
KEV
Not listed

Published

March 25, 2026

Last Modified

September 9, 2026

Advisory Details (9)

Auto-updated Jul 3, 2026
Patch available. Sources: github_commit, github, redhat.
redhat

2451444 – (CVE-2026-29785) CVE-2026-29785 github.com/nats-io/nats-server: NATS-Server: Denial of Service via leafnode compression

https://bugzilla.redhat.com/show_bug.cgi?id=2451444
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-29785
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:23345
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:22347
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:21769
githubMentions a patch (unverified)

leafnode pre-auth server panic DoS · Advisory · nats-io/nats-server · GitHub

https://github.com/nats-io/nats-server/security/advisories/GHSA-52jh-2xxh-pwh6
github_commit

commit a1488de6f2ba (nats-io/nats-server)

Fix landed in nats-io/nats-server commit a1488de6f2ba — awaiting tagged release

https://github.com/nats-io/nats-server/commit/a1488de6f2ba6e666aef0f9cce0016f7f167d6a8

Patch Availability(3)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/nats-io/nats-server—
  • every version on: no fix on record
—
github.com/nats-io/nats-server/v2—
  • every version up to 2.11.14: fixed in 2.11.14
  • 2.12.0-RC.1 up to 2.12.5: fixed in 2.12.5
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nats-server2.10.1-1 ... 2.9.19-1 (15 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nats-server2.10.27-1 ... 2.14.6-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nats-server2.10.27-1, 2.12.4-1
  • every version up to 2.12.6-1: fixed in 2.12.6-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:47 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:42 UTCEPSS rescore
  6. 2026-10-04 23:21 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-29 07:15 UTCOSV refresh
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 19:27 UTCEPSS rescore
  18. 2026-09-17 19:30 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-12 15:01 UTCEPSS rescore
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-09 13:42 UTCEG score recompute
Show 75 more
  1. 2026-09-09 13:42 UTCVendor advisory
  2. 2026-09-09 12:40 UTCEG score recompute
  3. 2026-09-09 12:40 UTCVendor advisory
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-07 13:24 UTCEG score recompute
  7. 2026-09-07 13:24 UTCVendor advisory
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-24 13:31 UTCEG score recompute
  23. 2026-08-24 13:31 UTCVendor advisory
  24. 2026-08-24 12:27 UTCEG score recompute
  25. 2026-08-24 12:27 UTCVendor advisory
  26. 2026-08-23 00:19 UTCEPSS rescore
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-20 22:55 UTCEPSS rescore
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-19 17:03 UTCEPSS rescore
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-17 12:21 UTCEG score recompute
  34. 2026-08-17 12:21 UTCVendor advisory
  35. 2026-08-17 12:13 UTCEG score recompute
  36. 2026-08-17 12:13 UTCVendor advisory
  37. 2026-08-16 14:56 UTCEPSS rescore
  38. 2026-08-16 10:13 UTCEG score recompute
  39. 2026-08-16 10:13 UTCVendor advisory
  40. 2026-08-16 02:14 UTCEPSS rescore
  41. 2026-08-15 01:30 UTCEPSS rescore
  42. 2026-08-15 00:17 UTCVendor advisory
  43. 2026-08-14 13:28 UTCEG score recompute
  44. 2026-08-14 13:28 UTCVendor advisory
  45. 2026-08-14 12:30 UTCEG score recompute
  46. 2026-08-14 12:30 UTCVendor advisory
  47. 2026-08-14 06:31 UTCEG score recompute
  48. 2026-08-14 06:31 UTCVendor advisory
  49. 2026-08-13 22:00 UTCEPSS rescore
  50. 2026-08-12 20:48 UTCEG score recompute
  51. 2026-08-12 20:48 UTCVendor advisory
  52. 2026-08-12 13:50 UTCEPSS rescore
  53. 2026-08-11 20:52 UTCEG score recompute
  54. 2026-08-11 20:52 UTCVendor advisory
  55. 2026-08-11 13:42 UTCEPSS rescore
  56. 2026-08-11 03:55 UTCEG score recompute
  57. 2026-08-11 03:55 UTCVendor advisory
  58. 2026-08-11 00:00 UTCEPSS rescore
  59. 2026-08-10 13:22 UTCEG score recompute
  60. 2026-08-10 13:22 UTCVendor advisory
  61. 2026-08-10 12:27 UTCEG score recompute
  62. 2026-08-10 12:27 UTCVendor advisory
  63. 2026-08-10 03:45 UTCVendor advisory
  64. 2026-08-09 16:56 UTCEG score recompute
  65. 2026-08-09 16:56 UTCVendor advisory
  66. 2026-08-09 13:46 UTCEPSS rescore
  67. 2026-08-09 06:07 UTCEG score recompute
  68. 2026-08-09 06:07 UTCVendor advisory
  69. 2026-08-08 16:37 UTCEPSS rescore
  70. 2026-08-08 03:15 UTCEG score recompute
  71. 2026-08-08 03:15 UTCVendor advisory
  72. 2026-08-07 16:27 UTCVendor advisory
  73. 2026-08-06 18:50 UTCEG score recompute
  74. 2026-08-06 18:50 UTCVendor advisory
  75. 2026-08-06 13:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-29785?
CVE-2026-29785 is a high vulnerability published on March 25, 2026. 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…
When was CVE-2026-29785 disclosed?
CVE-2026-29785 was first published on March 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-29785 actively exploited?
CVE-2026-29785 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29785?
CVE-2026-29785 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-29785?
A fix for CVE-2026-29785 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-29785 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-29785

Explore →

Is Your Infrastructure Affected by CVE-2026-29785?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.