CVE-2026-68119

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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: 0%CVSS: 7.5Exploit: 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:

tcp: initialize standalone TCP-AO response padding

tcp_v4_send_ack() and tcp_v6_send_response() construct standalone TCP responses with TCP-AO options. The option length carries the actual MAC length, but the TCP header length includes the option rounded up to a four-byte boundary.

tcp_ao_hash_hdr() writes the MAC only. Thus, when the MAC length is not four-byte aligned, the one to three bytes after the MAC are left uninitialized and may be transmitted. For the normal TCP-AO hashing mode, those bytes also have to be initialized before computing the MAC.

Initialize only the alignment padding in the TCP-AO branches, before hashing the header. Use TCPOPT_NOP, as in the normal TCP-AO output path. This avoids adding work to non-AO TCP responses while preserving a valid authenticated header.

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

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

tcp: initialize standalone TCP-AO response padding - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: initialize standalone TCP-AO response padding - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: initialize standalone TCP-AO response padding - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: initialize standalone TCP-AO response padding - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a859b280441fb02f64ed4037f03d5c0c34a7a595

Vendor Advisories for CVE-2026-68119(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 30× in last 7d / 42× 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 03:29 UTCEG score recompute
  2. 2026-08-21 03:29 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:17 UTCGHSA enrichment
  5. 2026-08-20 00:11 UTCEG score recompute
  6. 2026-08-20 00:11 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:59 UTCGHSA enrichment
  9. 2026-08-18 21:47 UTCEG score recompute
  10. 2026-08-18 21:47 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 08:35 UTCGHSA enrichment
  13. 2026-08-17 19:22 UTCEG score recompute
  14. 2026-08-17 19:22 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 05:41 UTCEG score recompute
  17. 2026-08-17 05:41 UTCGHSA enrichment
  18. 2026-08-17 05:12 UTCEG score recompute
  19. 2026-08-17 05:12 UTCGHSA enrichment
  20. 2026-08-16 17:39 UTCEG score recompute
  21. 2026-08-16 17:39 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 04:18 UTCEG score recompute
  24. 2026-08-16 04:18 UTCGHSA enrichment
  25. 2026-08-15 15:06 UTCGHSA enrichment
Show 17 more
  1. 2026-08-15 01:54 UTCEG score recompute
  2. 2026-08-15 01:54 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 12:43 UTCEG score recompute
  5. 2026-08-14 12:43 UTCGHSA enrichment
  6. 2026-08-13 23:31 UTCEG score recompute
  7. 2026-08-13 23:31 UTCGHSA enrichment
  8. 2026-08-13 22:46 UTCEG score recompute 7.50
  9. 2026-08-13 22:46 UTCGHSA enrichment
  10. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 10:06 UTCEG score recompute
  13. 2026-08-13 10:06 UTCGHSA enrichment
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-10 13:24 UTCNVD update
  16. 2026-08-10 12:21 UTCEG score recompute
  17. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68119?
CVE-2026-68119 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: tcp: initialize standalone TCP-AO response padding tcpv4sendack() and tcpv6sendresponse() construct standalone TCP responses with TCP-AO options. The option length carries the actual MAC length, but the TCP header length includes…
When was CVE-2026-68119 disclosed?
CVE-2026-68119 was first published in the National Vulnerability Database on August 10, 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-68119 actively exploited?
CVE-2026-68119 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 69.4% of all scored CVEs.
What is the CVSS score of CVE-2026-68119?
CVE-2026-68119 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-68119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68119, 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-68119

Explore →

Is Your Infrastructure Affected by CVE-2026-68119?

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