CVE-2026-12413

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

An invalidly formatted IKEv2 fragment causes the Libreswan pluto daemon to crash and restart. Continued exploitation would cause a denial of service. The function reassemble_v2_incoming_fragments() would ignore unknown outer payloads but still store these in a fixed size array msg_digest.digest[PAYLIMIT]. An off-by-one error in the assertion PASSERT(logger, md->digest_roof < elemsof(md->digest)) causes the daemon to abort. No remote code execution is possible. Any configuration that allows IKEv2 connections that do not set fragmentation=no are vulnerable. IKEv1 is not affected.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic
https://libreswan.org/security/CVE-2026-12413/CVE-2026-12413.txt
generic

Index of /security/CVE-2026-12413/

https://libreswan.org/security/CVE-2026-12413/

Vendor Advisories for CVE-2026-12413(13)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-4.19.9.6.202609021231-02026-09-09redhat
redhatrhcos-4.21.9.6.202609021100-02026-09-08redhat
redhatrhcos-4.20.9.6.202609021029-02026-09-08redhat
redhatlibreswan-0:4.9-5.el9_2.52026-08-31redhat
redhatlibreswan-0:4.12-3.el9_4.22026-08-31redhat
redhatlibreswan-0:4.15-8.el9_6.12026-08-20redhat
redhatlibreswan-0:5.2-1.el10_0.52026-08-17redhat
redhatlibreswan-0:4.12-2.el8_10.62026-07-27redhat
redhatlibreswan-0:4.15-10.el9_82026-07-27redhat
redhatlibreswan-0:5.3.2-1.el10_22026-07-27redhat
redhatlibreswan-0:5.3.2-1.el9fdp2026-07-27redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libreswan4.10-1 ... 5.2-2.4 (27 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libreswan4.10-2 ... 5.2-2.5 (18 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4, 5.2-2.5——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.45.2-2.5—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 74× 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 283 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-12413?
CVE-2026-12413 is a high vulnerability published on July 2, 2026. An invalidly formatted IKEv2 fragment causes the Libreswan pluto daemon to crash and restart. Continued exploitation would cause a denial of service. The function reassemblev2incomingfragments() would ignore unknown outer payloads but still store these in a fixed size array…
When was CVE-2026-12413 disclosed?
CVE-2026-12413 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12413 actively exploited?
CVE-2026-12413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.7% of all scored CVEs.
What is the CVSS score of CVE-2026-12413?
CVE-2026-12413 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-12413?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12413, 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-12413

Explore →

Is Your Infrastructure Affected by CVE-2026-12413?

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

Start Free Scan →Browse All CVEs