CVE-2026-86848

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-101507 (ENISA EUVD) · GHSA-rr86-5jrg-p5m3 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in DPDK lib/vhost vhost-crypto. The indirect-descriptor snapshot double-fetches a guest descriptor next index, allowing a malicious guest to cause an out-of-bounds access in the host backend.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

November 11, 2026

Advisory Details (2)

Auto-updated Oct 14, 2026
Patch available. Sources: redhat.
Red Hat

2529853 – (CVE-2026-86848) CVE-2026-86848 dpdk: dpdk: Time-of-check/time-of-use vulnerability allowing guest-triggered out-of-bounds write in vhost-crypto

https://bugzilla.redhat.com/show_bug.cgi?id=2529853
Red HatMentions a patch (unverified)

CVE-2026-86848 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-86848

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdpdk-0:23.11-3.el8_102026-11-09redhat
redhatdpdk-2:25.11-2.el10_22026-11-03redhat
redhatdpdk-2:25.11-2.el9_82026-11-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dpdk22.11.1-2 ... 25.11.4-1 (44 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dpdk24.11.2-2, 24.11.3-1, 24.11.3-1~deb13u1, 24.11.3-2, 24.11.4-0+deb13u1
  • every version up to 24.11.8-0+deb13u1: fixed in 24.11.8-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dpdk24.11.2-2 ... 25.11.3-1 (9 versions)
  • every version up to 25.11.4-1: fixed in 25.11.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 17× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-11-11 14:27 UTCEchelonGraph re-scored
  5. 2026-11-11 14:27 UTCVendor advisory
  6. 2026-11-11 14:27 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-11-11 13:59 UTCEchelonGraph re-scored
  8. 2026-11-11 13:59 UTCVendor advisory
  9. 2026-11-11 13:59 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-11-11 13:28 UTCEchelonGraph re-scored
  11. 2026-11-11 13:28 UTCVendor advisory
  12. 2026-11-11 13:28 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-11-11 12:24 UTCEchelonGraph re-scored
  14. 2026-11-11 12:24 UTCVendor advisory
  15. 2026-11-11 12:24 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-11-09 10:27 UTCEchelonGraph re-scored
  18. 2026-11-09 10:27 UTCVendor advisory
  19. 2026-11-09 10:27 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-11-09 09:51 UTCEchelonGraph re-scored
  21. 2026-11-09 09:51 UTCVendor advisory
  22. 2026-11-09 09:51 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 47 more
  1. 2026-11-05 00:27 UTCEchelonGraph re-scored
  2. 2026-11-05 00:27 UTCVendor advisory
  3. 2026-11-05 00:27 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-05 00:00 UTCEchelonGraph re-scored
  5. 2026-11-05 00:00 UTCVendor advisory
  6. 2026-11-05 00:00 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-11-04 11:27 UTCEchelonGraph re-scored
  9. 2026-11-04 11:27 UTCVendor advisory
  10. 2026-11-04 11:27 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-11-04 10:26 UTCEchelonGraph re-scored
  12. 2026-11-04 10:26 UTCVendor advisory
  13. 2026-11-04 10:26 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-11-03 19:27 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-11-03 18:28 UTCEchelonGraph re-scored
  16. 2026-11-03 18:28 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-11-03 18:02 UTCEchelonGraph re-scored
  18. 2026-11-03 18:02 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-11-03 16:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-10-31 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-10-30 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-10-29 13:05 UTCEchelonGraph re-scored
  24. 2026-10-29 13:05 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-28 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  26. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  27. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  28. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-10-25 13:54 UTCEchelonGraph re-scored
  30. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  32. 2026-10-22 03:56 UTCEchelonGraph re-scored
  33. 2026-10-22 03:56 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  34. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  35. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  36. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-10-18 03:04 UTCEchelonGraph re-scored
  38. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  39. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  40. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  41. 2026-10-14 20:33 UTCEchelonGraph re-scored
  42. 2026-10-14 20:33 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  43. 2026-10-14 19:45 UTCEchelonGraph re-scored
  44. 2026-10-14 19:44 UTCGHSA enrichmentGHSA-rr86-5jrg-p5m3 · GitHub severity HIGH · GitHub CVSS 8.8
  45. 2026-10-14 18:26 UTCEchelonGraph re-scored
  46. 2026-10-14 17:56 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
  47. 2026-10-14 17:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86848?
CVE-2026-86848 is a high-severity vulnerability; its CVE record was published on October 14, 2026. A flaw was found in DPDK lib/vhost vhost-crypto. The indirect-descriptor snapshot double-fetches a guest descriptor next index, allowing a malicious guest to cause an out-of-bounds access in the host backend.
When was CVE-2026-86848 made public?
CVE-2026-86848 was made public on October 14, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 14, 2026. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-86848 actively exploited?
CVE-2026-86848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86848?
CVE-2026-86848 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86848?
A fix for CVE-2026-86848 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-86848 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-86848

Explore →

Is Your Infrastructure Affected by CVE-2026-86848?

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