CVE-2026-28964

CVE-2026-28964 is a high-severity vulnerability in Apple Ipados with a CVSS 3.x base score of 7.5. 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-451.

Key facts

Description

An inconsistent user interface issue was addressed with improved state management. This issue is fixed in iOS 26.5 and iPadOS 26.5, visionOS 26.5. An app may be able to access sensitive user data.

Frequently asked questions

What is CVE-2026-28964?
An inconsistent user interface issue was addressed with improved state management. This issue is fixed in iOS 26.5 and iPadOS 26.5, visionOS 26.5. An app may be able to access sensitive user data.
How severe is CVE-2026-28964?
CVE-2026-28964 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-28964 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-28964?
CVE-2026-28964 primarily affects Apple Ipados. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-28964?
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.
Does CVE-2026-28964 have an EU (EUVD) identifier?
Yes. CVE-2026-28964 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-29268.
When was CVE-2026-28964 published?
CVE-2026-28964 was published on 2026-05-11 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Apple Ipados

All CVEs affecting Apple Ipados →

Other CWE-451 vulnerabilities

Browse all CWE-451 vulnerabilities →