CVE-2026-12413

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
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
44.9%
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(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 62× 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.

  1. 2026-07-23 03:05 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 23:59 UTCVendor advisory
  9. 2026-07-16 23:59 UTCGHSA enrichment
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-16 11:34 UTCVendor advisory
  12. 2026-07-16 11:34 UTCGHSA enrichment
  13. 2026-07-15 23:06 UTCVendor advisory
  14. 2026-07-15 23:06 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 10:41 UTCVendor advisory
  17. 2026-07-15 10:40 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 22:12 UTCVendor advisory
  20. 2026-07-14 22:12 UTCGHSA enrichment
  21. 2026-07-14 09:46 UTCVendor advisory
  22. 2026-07-14 09:46 UTCGHSA enrichment
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 21:19 UTCGHSA enrichment
  25. 2026-07-13 08:52 UTCGHSA enrichment
Show 37 more
  1. 2026-07-13 06:12 UTCEPSS rescore
  2. 2026-07-12 20:27 UTCVendor advisory
  3. 2026-07-12 20:27 UTCGHSA enrichment
  4. 2026-07-12 08:01 UTCVendor advisory
  5. 2026-07-12 08:01 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 19:35 UTCVendor advisory
  8. 2026-07-11 19:35 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 07:10 UTCVendor advisory
  11. 2026-07-11 07:10 UTCGHSA enrichment
  12. 2026-07-10 18:44 UTCVendor advisory
  13. 2026-07-10 18:44 UTCGHSA enrichment
  14. 2026-07-10 06:18 UTCGHSA enrichment
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 17:52 UTCGHSA enrichment
  17. 2026-07-09 05:25 UTCGHSA enrichment
  18. 2026-07-08 17:00 UTCGHSA enrichment
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-08 15:15 UTCEPSS rescore
  21. 2026-07-08 04:35 UTCGHSA enrichment
  22. 2026-07-07 16:08 UTCGHSA enrichment
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-07 03:41 UTCGHSA enrichment
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 15:11 UTCGHSA enrichment
  27. 2026-07-06 02:43 UTCGHSA enrichment
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-05 14:17 UTCGHSA enrichment
  30. 2026-07-05 02:30 UTCEPSS rescore
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-05 01:51 UTCGHSA enrichment
  33. 2026-07-04 13:26 UTCGHSA enrichment
  34. 2026-07-04 01:00 UTCGHSA enrichment
  35. 2026-07-03 12:35 UTCGHSA enrichment
  36. 2026-07-03 00:07 UTCEG score recompute
  37. 2026-07-03 00:06 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

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 44.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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