CVE-2026-58213

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% 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
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (8)

Auto-updated Jul 8, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available

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_pr

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_pr

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 / EcosystemFixed in / PatchReleasedSource
redhatnats-server2-14-main-2.14.3-1.hum12026-07-06redhat
redhatnats-server2-12-main-2.12.12-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 rangeFixed inDependents
nats-server2.10.1-1 ... 2.9.19-1 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.27-1, 2.12.4-1, 2.12.6-1, 2.14.1-1, 2.14.3-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.27-1, 2.12.4-1, 2.12.6-12.14.1-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 64× 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 108 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58213?
CVE-2026-58213 is a high vulnerability 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 CVE-2026-58213 disclosed?
CVE-2026-58213 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58213 actively exploited?
CVE-2026-58213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.3% of all scored CVEs.
What is the CVSS score of CVE-2026-58213?
CVE-2026-58213 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-58213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58213, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs