How severe is CVE-2026-86563?

CVE-2026-86563 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-86563 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-86563?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-86563 published?

CVE-2026-86563 was published on 2026-10-14.

CVE-2026-86563

CVE-2026-86563 is a high-severity vulnerability with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-131.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 0% (5th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-131
Published: 2026-10-14
Last modified: 2026-10-14

Description

A flaw was found in DPDK lib/vhost. A double-offset bug in vhost log mapping calculation can lead to incorrect memory access.

Frequently asked questions

What is CVE-2026-86563?: A flaw was found in DPDK lib/vhost. A double-offset bug in vhost log mapping calculation can lead to incorrect memory access.
How severe is CVE-2026-86563?: CVE-2026-86563 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-86563 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-86563?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-86563 published?: CVE-2026-86563 was published on 2026-10-14.

References

Other CWE-131 (Incorrect Calculation of Buffer Size) vulnerabilities

CVE-2026-1949 — Critical (CVSS 9.8): Delta Electronics AS320T has incorrect calculation of the buffer size on the stack in the GET/PUT request handler of…
CVE-2026-31478 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: ksmbd: replace hardcoded hdr2_len with offsetof()…
CVE-2026-20911 — Critical (CVSS 9.8): A heap-based buffer overflow vulnerability exists in the HuffTable::initval functionality of LibRaw Commit 0b56545 and…
CVE-2025-1861 — Critical (CVSS 9.8): In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before 8.4.5, when…
CVE-2023-5941 — Critical (CVSS 9.8): In versions of FreeBSD 12.4-RELEASE prior to 12.4-RELEASE-p7 and FreeBSD 13.2-RELEASE prior to 13.2-RELEASE-p5 the…
CVE-2022-33211 — Critical (CVSS 9.8): memory corruption in modem due to improper check while calculating size of serialized CoAP message

Browse all CWE-131 (Incorrect Calculation of Buffer Size) vulnerabilities →