CVE-2026-86913 json
A use after free issue was addressed with improved memory management.
published 23d ago modified 2d ago also EUVD-2026-104715
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
A use after free issue was addressed with improved memory management. This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7, tvOS 27, visionOS 27, watchOS 27. Processing a maliciously crafted media file may lead to unexpected app termination or corrupt process memory.
Patch / fix
- Apple iOS and iPadOS 26.7, 27
- Apple macOS 15.8, 26.7, 27
- Apple tvOS 27
- Apple visionOS 27
- Apple watchOS 27
Is CVE-2026-86913 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 22d ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
support.apple.com
/en-us/149034
vendor-advisory
-
support.apple.com
/en-us/149035
vendor-advisory
-
support.apple.com
/en-us/149036
vendor-advisory
-
support.apple.com
/en-us/149037
vendor-advisory
-
support.apple.com
/en-us/149038
vendor-advisory
-
support.apple.com
/en-us/149041
vendor-advisory
-
support.apple.com
/en-us/149042
vendor-advisory
-
support.apple.com
/en-us/149043
vendor-advisory
Sources
- CVE List CVE-2026-86913
- NVD CVE-2026-86913
Fencer Intel 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.