Menu

Star on GitHub · 3.2k

CVE-2026-62430

7.5 · HIGH

Accesses to the CMOS memory contents are done using an indirect IO port pair.

Published Jul 28, 2026CWE-362EPSS 0.24%

Overview

CVE-2026-62430 is a high-severity vulnerability. It was published on July 28, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Accesses to the CMOS memory contents are done using an indirect IO port

pair. Therefore Xen needs to cache the guest chosen index, and one of

the usages of the index didn't take the necessary locking to avoid

concurrent changes. As a result, a guest could change the index after

it being checked, causing a subsequent out-of-bound read access to the

contents of an array.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-62430?

CVE-2026-62430 is a high-severity vulnerability. It was published on July 28, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

How severe is CVE-2026-62430?

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-62430?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-62430?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-62430 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all