Quick answers
- Is CVE-2026-86848 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86848 being exploited in the wild.
- How severe is CVE-2026-86848?
- High severity, with a CVSS score of 8.8, published 14 October 2026.
- Which products and versions are affected?
- DPDK <UNKNOWN>.
- Is there a fix for CVE-2026-86848?
- No fixed version is recorded yet. Do not attach a virtio-crypto vhost-user backend to untrusted guests. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86848 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-86848?
- Check whether you run DPDK at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Do not attach a virtio-crypto vhost-user backend to untrusted guests.
Technical details
The vulnerability is a time-of-check/time-of-use (TOCTOU) race condition in the vhost-crypto indirect-descriptor snapshot code that double-fetches a guest descriptor next index, leading to out-of-bounds access. A guest with a virtio-crypto vhost-user device attached can trigger this flaw with low privileges and no user interaction required. This affects host memory confidentiality, integrity, and availability.
Affected products
- DPDK DPDK <UNKNOWN>
Timeline
- 2026-10-14: disclosed