CVE-2026-86950
Added to CISA's Known Exploited catalogue; the federal remediation date of 2026-10-02 has passed. An authority ruling of this kind is not conditional on a severity score.
CVE record, CISA KEV and EPSS as of 2026-10-25.
CVEs like this one computed, by meaning
What to do now held facts and links
- CISA requires: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. The federal deadline has passed: overdue since 2026-10-13. CISA KEVCISA's notes for this entry: support.apple.com support.apple.com support.apple.com cisa.gov
- Upgrade to the fixed version for your release line, or later: 26.7.1; 15.8.1 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 26.7.1 and iPadOS 26.7.1, macOS Sequoia 15.8.1, macOS Tahoe 26.7.1. Processing a maliciously crafted file may lead to arbitrary code execution. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27.
- weakness
- Processing a maliciously crafted file may lead to arbitrary code execution. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27.
- affected
- Apple iOS and iPadOS; Apple macOS
- published ranges
- apple ipados < 26.7.1; apple iphone os < 26.7.1; apple macos < 15.8.1; apple macos >= 26.0 < 26.7.1
- fixed in
- 26.7.1; 15.8.1
- assigned by
- apple
- published
- 2026-09-28
check us support.apple.com support.apple.com support.apple.com
Authority held, dated
- CISA KEV
- listed
- added
- 2026-09-29
- remediation due
- 2026-10-13
- ransomware use
- unknown
- remediation status
- overdue since 2026-10-13
- exploit code
- 1 public proof-of-concept repository, first seen 2026-09-29 (PoC-in-GitHub).
A KEV listing is an assertion of observed exploitation. It is the only element on this page that makes that claim.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 29 Sep 2026 | 0.00812 | |
| 30 Sep 2026 | 0.01242 | |
| 25 Oct 2026 | 0.26166 | crossed 0.10 |
3 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Listed, added 2026-09-29. Due 2026-10-13. A changed deadline or a change in ransomware use changes this brief.
- exploit probability
- 0.26 on 2026-10-25 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 50% (0.50). Crossing a line changes this brief.
- fix
- Held: 26.7.1; 15.8.1. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-86950', '2026-10-31T23:59:59.999999Z', now());