Quick answers
- Is CVE-2026-86845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86845 being exploited in the wild.
- How severe is CVE-2026-86845?
- Medium severity, with a CVSS score of 6.5, published 14 October 2026.
- Which products and versions are affected?
- DPDK Project DPDK.
- Is there a fix for CVE-2026-86845?
- 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-86845 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-86845?
- Check whether you run DPDK Project DPDK. 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
A use-after-free and type confusion vulnerability exists in DPDK's lib/vhost vhost-crypto backend where session cleanup leaves a stale cached session pointer that the data path fails to validate before use. An attacker with access to a virtio-crypto vhost-user device can trigger the flaw to cause denial of service or potential code execution. The vulnerability is triggered by local attack vector with low privilege requirements.
Affected products
- DPDK Project DPDK
Timeline
- 2026-10-14: disclosed