CVE-2026-58213

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-42383 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.1 and 2.12.9, an MQTT client could include protocol control characters in subscription filters that were later forwarded as NATS protocol data to route or leafnode connections, corrupting the forwarded protocol stream and allowing injection of unintended NATS protocol operations. This issue is fixed in versions 2.14.1 and 2.12.9.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

October 25, 2026

Advisory Details (8)

Auto-updated Jul 8, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

MQTT SUBSCRIBE Protocol Injection via Leaf Node/Route Forwarding allows arbitrary NATS command injection (CWE-74) · Advisory · nats-io/nats-server · GitHub

Affected: v2.14.1 and v2.12.9.

https://github.com/nats-io/nats-server/security/advisories/GHSA-qrcv-3558-gj4f
GitHub release Patch Available

Release v2.14.1

Patch available: nats-io/nats-server v2.14.1

https://github.com/nats-io/nats-server/releases/tag/v2.14.1
GitHub release Patch Available

Release v2.12.9

Patch available: nats-io/nats-server v2.12.9

https://github.com/nats-io/nats-server/releases/tag/v2.12.9
GitHub pull request

Cherry-picks for 2.12.9-RC.1

Fix merged in nats-io/nats-server PR #8164 on 2026-05-14 — awaiting tagged release

https://github.com/nats-io/nats-server/pull/8164
GitHub pull request

Cherry-picks for 2.14.1-RC.1

Fix merged in nats-io/nats-server PR #8163 on 2026-05-14 — awaiting tagged release

https://github.com/nats-io/nats-server/pull/8163
GitHub commit

commit f14856b9e57a (nats-io/nats-server)

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

https://github.com/nats-io/nats-server/commit/f14856b9e57a36818f43851cb69b6e33670885c9
GitHub commit

commit 64ebae40051e (nats-io/nats-server)

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

https://github.com/nats-io/nats-server/commit/64ebae40051ee497c481e10f316238faf0de1736
GitHub commit

commit 366837cfc65a (nats-io/nats-server)

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

https://github.com/nats-io/nats-server/commit/366837cfc65ab9ccb4f98193c65e8daf238582d8

Vendor Advisories for CVE-2026-58213(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnats-server2-12-main-2.12.12-1.hum12026-07-06redhat
redhatnats-server2-14-main-2.14.3-1.hum12026-07-06redhat

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

(3 across 3 ecosystems)
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, 2.12.6-1
  • every version up to 2.14.1-1: fixed in 2.14.1-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-58213?
CVE-2026-58213 is a high-severity vulnerability; its CVE record was published on July 8, 2026. NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.1 and 2.12.9, an MQTT client could include protocol control characters in subscription filters that were later forwarded as NATS protocol data to route or leafnode connections, corrupting…
When was the CVE record for CVE-2026-58213 published?
The CVE record for CVE-2026-58213 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-58213 actively exploited?
CVE-2026-58213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58213?
CVE-2026-58213 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58213?
A fix for CVE-2026-58213 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58213 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-58213

Explore →

Is Your Infrastructure Affected by CVE-2026-58213?

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