CVE-2023-41061
Apple iOS, iPadOS, and watchOS Wallet Code Execution Vulnerability
Apple iOS, iPadOS, and watchOS
A validation issue was addressed with improved logic. This issue is fixed in watchOS 9.6.2, iOS 16.6.1 and iPadOS 16.6.1. A maliciously crafted attachment may result in arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 11 September 2023. US federal agencies were required to remediate it by 2 October 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 4.4%, which is higher than 91.4% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2023-41061 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2023-41061.
What does CVE-2023-41061 affect?
CVE-2023-41061 affects Apple iOS, iPadOS, and watchOS. A validation issue was addressed with improved logic. This issue is fixed in watchOS 9.6.2, iOS 16.6.1 and iPadOS 16.6.1. A maliciously crafted attachment may result in arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited.
How severe is CVE-2023-41061?
CVE-2023-41061 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 4.4%, higher than 91.4% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 October 2023.
How should organisations respond to CVE-2023-41061?
Apply the vendor patch for Apple iOS, iPadOS, and watchOS as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.