CVE-2025-24141

CVE-2025-24141 is a low-severity vulnerability in Apple Ipados with a CVSS 3.x base score of 3.3. 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-863.

Key facts

Description

An authentication issue was addressed with improved state management. This issue is fixed in iOS 18.3 and iPadOS 18.3. An attacker with physical access to an unlocked device may be able to access Photos while the app is locked.

Frequently asked questions

What is CVE-2025-24141?
An authentication issue was addressed with improved state management. This issue is fixed in iOS 18.3 and iPadOS 18.3. An attacker with physical access to an unlocked device may be able to access Photos while the app is locked.
How severe is CVE-2025-24141?
CVE-2025-24141 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-24141 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-24141?
CVE-2025-24141 primarily affects Apple Ipados. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-24141?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-24141 have an EU (EUVD) identifier?
Yes. CVE-2025-24141 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-3649.
When was CVE-2025-24141 published?
CVE-2025-24141 was published on 2025-01-27 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Apple Ipados

All CVEs affecting Apple Ipados →

Other CWE-863 (Incorrect Authorization) vulnerabilities

Browse all CWE-863 (Incorrect Authorization) vulnerabilities →