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 — Patch released 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
46%
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(8)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibreswan-0:4.15-8.el9_6.12026-08-20redhat
redhatlibreswan-0:5.2-1.el10_0.52026-08-17redhat
redhatlibreswan-0:5.3.2-1.el9fdp2026-07-27redhat
redhatlibreswan-0:5.3.2-1.el10_22026-07-27redhat
redhatlibreswan-0:4.12-2.el8_10.62026-07-27redhat
redhatlibreswan-0:4.15-10.el9_82026-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.4 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libreswan5.2-2.2, 5.2-2.3, 5.2-2.4——

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 165× 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 238 total refreshes for this CVE.

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

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 54.0% 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