CVE-2023-41071 json
A use-after-free issue was addressed with improved memory management.
published 2023-09-26 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-45592
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
A use-after-free issue was addressed with improved memory management. This issue is fixed in tvOS 17, iOS 17 and iPadOS 17, watchOS 10, macOS Ventura 13.6. An app may be able to execute arbitrary code with kernel privileges.
Patch / fix
- Apple iOS and iPadOS 17
- Apple macOS 13.6
- Apple tvOS 17
- Apple watchOS 10
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple watchOS
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
support.apple.com
/en-us/HT213938
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213931
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213936
release-notes, vendor-advisory
-
support.apple.com
/en-us/HT213937
release-notes, vendor-advisory
-
seclists.org
/fulldisclosure/2023/Oct/5
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2023/Oct/10
mailing-list, third-party-advisory
- seclists.org /fulldisclosure/2023/Oct/8
- seclists.org /fulldisclosure/2023/Oct/9
- support.apple.com /kb/HT213931
- support.apple.com /kb/HT213938
- support.apple.com /kb/HT213937
- support.apple.com /kb/HT213936
Sources
- CVE List CVE-2023-41071
- NVD CVE-2023-41071
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.