CVE-2026-74707

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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:

xsk: validate metadata when processing requests

The zero-copy path validates TX metadata while obtaining the descriptor context, then reads it again later when preparing the hardware request. User space can change the metadata between those operations and bypass the original validation.

Validate the metadata in xsk_tx_metadata_request() and use the resulting flags snapshot for every feature check. Read request fields once so all zero-copy drivers process only values observed after successful validation.

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
3%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (3)

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

xsk: validate metadata when processing requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/849b1664dbda1cf6c63e0fd4f9dec23782b8c851
generic

xsk: validate metadata when processing requests - kernel/git/stable/linux.git - Linux kernel stable tree

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

xsk: validate metadata when processing requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5fd121971912dee2f5af1efec64462ac722deb17

Vendor Advisories for CVE-2026-74707(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 26× in last 7d / 29× 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-30 05:07 UTCEG score recompute
  2. 2026-08-30 05:07 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 17:36 UTCGHSA enrichment
  5. 2026-08-29 05:04 UTCEG score recompute
  6. 2026-08-29 05:04 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 17:33 UTCGHSA enrichment
  9. 2026-08-28 05:45 UTCGHSA enrichment
  10. 2026-08-27 18:16 UTCEG score recompute
  11. 2026-08-27 18:16 UTCGHSA enrichment
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-27 05:19 UTCGHSA enrichment
  14. 2026-08-26 17:49 UTCEG score recompute
  15. 2026-08-26 17:49 UTCGHSA enrichment
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-26 05:24 UTCGHSA enrichment
  18. 2026-08-25 17:57 UTCEG score recompute
  19. 2026-08-25 17:56 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 06:29 UTCEG score recompute
  22. 2026-08-25 06:29 UTCGHSA enrichment
  23. 2026-08-25 05:55 UTCEG score recompute▲ 7.80
  24. 2026-08-25 05:55 UTCGHSA enrichment
  25. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
Show 4 more
  1. 2026-08-24 14:18 UTCEPSS rescore
  2. 2026-08-22 16:24 UTCNVD update
  3. 2026-08-22 15:38 UTCEG score recompute
  4. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74707?
CVE-2026-74707 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: xsk: validate metadata when processing requests The zero-copy path validates TX metadata while obtaining the descriptor context, then reads it again later when preparing the hardware request. User space can change the metadata…
When was CVE-2026-74707 disclosed?
CVE-2026-74707 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74707 actively exploited?
CVE-2026-74707 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-74707?
CVE-2026-74707 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74707?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74707, 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-74707

Explore →

Is Your Infrastructure Affected by CVE-2026-74707?

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

Start Free Scan →Browse All CVEs