CVE-2026-74701

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:

net/openvswitch: check Ethernet header length in key_extract()

When a packet arrives on an ARPHRD_NONE device (e.g. TUN), ovs_flow_key_extract() trusts the user-provided skb->protocol field: if it is ETH_P_TEB, the packet is classified as MAC_PROTO_ETHERNET and key_extract() is called without ensuring the skb has ETH_HLEN (14) bytes of linear data. key_extract() unconditionally pulls 2 * ETH_ALEN bytes for MAC addresses and parse_ethertype() pulls 2 more, either of which triggers a kernel BUG in __skb_pull() when the linear area is too small.

kernel BUG at include/linux/skbuff.h:2848! RIP: 0010:key_extract+0xa7e/0xd90 net/openvswitch/flow.c:933 ovs_flow_key_extract+0x419/0xa70 ovs_vport_receive+0x222/0x390 netdev_frame_hook+0x3e0/0x630 tun_get_user+0x2d0c/0x38e0

Fixed by calling check_header() in key_extract() before accessing the Ethernet header.

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 (8)

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

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b8cfbb58b85bfa7a78fac47fdc77396cd01f699
generic

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/831471718f6e19aed1a330b03b53190a90e06466
generic

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81f9b09f0ea3ba9ab966dd17e9f32625a14555e9
generic

net/openvswitch: check Ethernet header length in key_extract() - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

Frequently asked(5)

What is CVE-2026-74701?
CVE-2026-74701 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net/openvswitch: check Ethernet header length in key_extract() When a packet arrives on an ARPHRD_NONE device (e.g. TUN), ovsflowkey_extract() trusts the user-provided skb->protocol field: if it is ETHPTEB, the packet is classified…
When was CVE-2026-74701 disclosed?
CVE-2026-74701 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-74701 actively exploited?
CVE-2026-74701 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-74701?
CVE-2026-74701 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74701?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74701, 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-74701

Explore →

Is Your Infrastructure Affected by CVE-2026-74701?

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

Start Free Scan →Browse All CVEs