CVE-2026-72400

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

seg6: validate SRH length before reading fixed fields

seg6_validate_srh() reads fixed SRH fields such as srh->type and srh->hdrlen before checking that the supplied length covers the fixed struct ipv6_sr_hdr fields.

The BPF SEG6 encap path reaches this with a BPF program-supplied pointer and length: bpf_lwt_push_encap() and the SEG6 local BPF END_B6 and END_B6_ENCAP actions call bpf_push_seg6_encap(), which forwards the length to seg6_validate_srh() with no minimum-size guard. A 2-byte SEG6 encap header can therefore make the validator read srh->type at offset 2 beyond the caller-supplied buffer.

Reject lengths shorter than the fixed SRH at the top of seg6_validate_srh(), before any field is read. This fixes the BPF helper path and keeps the common validator robust.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c9961336aa5ff83092f23e33ee86666a9dbd1b2a
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a75d99f46bf21b45965ce39c5cfb3b8bb5ffb1aa
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8dba7a94a269b88e500aafc25ad567ef6a423698
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/804bb969f194c93497ba632b98343794c6367fdc
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7247d05c987c3eec4bb7c2306dbd77ecdf3b7c73
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/715eb12e453df752f1b4baaf972c3acff0ab9402
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fc7069d39239978130c37ebceaec85c8948d3f1
generic

seg6: validate SRH length before reading fixed fields - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/071f1a38d7ddbadee29c09b9e3ee0ff3a61e6a0e

Vendor Advisories for CVE-2026-72400(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 28× 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-08-20 06:34 UTCGHSA enrichment
  2. 2026-08-19 18:39 UTCEG score recompute
  3. 2026-08-19 18:39 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 06:44 UTCGHSA enrichment
  6. 2026-08-18 18:48 UTCEG score recompute
  7. 2026-08-18 18:48 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 06:53 UTCGHSA enrichment
  11. 2026-08-17 18:59 UTCEG score recompute
  12. 2026-08-17 18:59 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 06:29 UTCEG score recompute
  15. 2026-08-17 06:29 UTCGHSA enrichment
  16. 2026-08-17 05:57 UTCEG score recompute 7.80
  17. 2026-08-17 05:57 UTCGHSA enrichment
  18. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-08-17 05:29 UTCEG score recompute
  20. 2026-08-17 05:29 UTCGHSA enrichment
  21. 2026-08-17 05:24 UTCMITRE cvelistV5
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 06:34 UTCGHSA enrichment
Show 3 more
  1. 2026-08-15 06:23 UTCNVD update
  2. 2026-08-15 06:05 UTCEG score recompute
  3. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72400?
CVE-2026-72400 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: seg6: validate SRH length before reading fixed fields seg6validatesrh() reads fixed SRH fields such as srh->type and srh->hdrlen before checking that the supplied length covers the fixed struct ipv6srhdr fields. The BPF SEG6 encap…
When was CVE-2026-72400 disclosed?
CVE-2026-72400 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72400 actively exploited?
CVE-2026-72400 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 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72400?
CVE-2026-72400 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72400?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72400, 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-72400

Explore →

Is Your Infrastructure Affected by CVE-2026-72400?

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