CVE-2026-68477

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.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:

ipvs: fix more places with wrong ipv6 transport offsets

Sashiko reports for more incorrect IPv6 transport offsets.

The app code for TCP was assuming IPv4 network header even after the ipvsh argument was provided. This can cause problems with apps over IPv6. As for the only official app in the kernel tree (FTP) this problem is harmless because we use Netfilter to mangle the FTP ports and we do not adjust the TCP seq numbers.

Also, provide correct offset of the ICMPV6 header in ip_vs_out_icmp_v6() for correct checksum checks when the IPv6 packet has extension headers.

CVSS v3
9.8
EG Score
9.8(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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
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

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95d4511d81b2b37e5d2bdde5d912e48243eae517
generic

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/905d7a363ade96a19f214815361e11981142c547
generic

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7350eb7ead172ae8024897d4b0f2e15c5318279c
generic

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/613ce63711b8d431bba90781f133c39a21684f87
generic

ipvs: fix more places with wrong ipv6 transport offsets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a9dc9b55b53d94613a587604b77d3b20024090c

Vendor Advisories for CVE-2026-68477(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 47× in last 7d / 47× 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-21 05:35 UTCGHSA enrichment
  2. 2026-08-21 01:27 UTCEG score recompute
  3. 2026-08-21 01:27 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 21:21 UTCGHSA enrichment
  6. 2026-08-20 17:14 UTCGHSA enrichment
  7. 2026-08-20 13:05 UTCGHSA enrichment
  8. 2026-08-20 08:50 UTCGHSA enrichment
  9. 2026-08-20 04:44 UTCGHSA enrichment
  10. 2026-08-20 00:37 UTCGHSA enrichment
  11. 2026-08-19 20:30 UTCEG score recompute
  12. 2026-08-19 20:30 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 16:23 UTCGHSA enrichment
  15. 2026-08-19 12:16 UTCGHSA enrichment
  16. 2026-08-19 08:09 UTCGHSA enrichment
  17. 2026-08-19 04:02 UTCGHSA enrichment
  18. 2026-08-18 23:54 UTCGHSA enrichment
  19. 2026-08-18 19:47 UTCGHSA enrichment
  20. 2026-08-18 15:40 UTCEG score recompute
  21. 2026-08-18 15:40 UTCGHSA enrichment
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 11:33 UTCGHSA enrichment
  25. 2026-08-18 07:26 UTCGHSA enrichment
Show 22 more
  1. 2026-08-18 03:19 UTCGHSA enrichment
  2. 2026-08-17 23:09 UTCGHSA enrichment
  3. 2026-08-17 19:03 UTCGHSA enrichment
  4. 2026-08-17 14:44 UTCEG score recompute
  5. 2026-08-17 14:44 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 10:37 UTCEG score recompute
  8. 2026-08-17 10:37 UTCGHSA enrichment
  9. 2026-08-17 06:30 UTCEG score recompute
  10. 2026-08-17 06:30 UTCGHSA enrichment
  11. 2026-08-17 06:01 UTCEG score recompute▲ 9.80
  12. 2026-08-17 06:01 UTCGHSA enrichment
  13. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-08-17 05:34 UTCEG score recompute
  15. 2026-08-17 05:34 UTCGHSA enrichment
  16. 2026-08-17 05:24 UTCMITRE cvelistV5
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-15 06:47 UTCGHSA enrichment
  20. 2026-08-15 06:23 UTCNVD update
  21. 2026-08-15 06:20 UTCEG score recompute
  22. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68477?
CVE-2026-68477 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ipvs: fix more places with wrong ipv6 transport offsets Sashiko reports for more incorrect IPv6 transport offsets. The app code for TCP was assuming IPv4 network header even after the ipvsh argument was provided. This can cause…
When was CVE-2026-68477 disclosed?
CVE-2026-68477 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-68477 actively exploited?
CVE-2026-68477 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 49.5% of all scored CVEs.
What is the CVSS score of CVE-2026-68477?
CVE-2026-68477 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68477?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68477, 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-68477

Explore →

Is Your Infrastructure Affected by CVE-2026-68477?

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

Start Free Scan →Browse All CVEs