CVE-2026-86987: Input Validation
Accelerate Framework. An out-of-bounds write issue was addressed with improved bounds checking.
Other sources
AccessorySetupKit. An authentication issue was addressed with improved state management.
— Apple
Accounts. A logging issue was addressed with improved data redaction.
— Apple
Accounts. A path handling issue was addressed with improved validation.
— Apple
Accounts. This issue was addressed with additional entitlement checks.
— Apple
An authorization issue was addressed with improved entitlement checks. This issue is fixed in iOS 27.2 and iPadOS 27.2. A remote attacker may be able to access sensitive user data.
— MITRE
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 27.2 - Upgrade
Upgrade
iOS and iPadOSto a version that resolves this vulnerability.Fixed in 27.2
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-86971
- CVE-2026-84493
- CVE-2026-113898
- CVE-2026-112446
- CVE-2026-112612
- CVE-2026-112692
- CVE-2026-113914
- CVE-2026-112690
- CVE-2026-86987
- CVE-2026-112696
- CVE-2026-84494
- CVE-2026-112416
- CVE-2026-112415
- CVE-2026-112454
- CVE-2026-112546
- CVE-2026-112705
- CVE-2026-112689
- CVE-2026-112470
- CVE-2026-112469
- CVE-2026-112468
- CVE-2026-112466
- CVE-2026-112566
- CVE-2026-113906
- CVE-2026-112678
- CVE-2026-112619
- CVE-2026-112701
- CVE-2026-86988
- CVE-2026-113910
- CVE-2026-113908
- CVE-2026-113912
- CVE-2026-113907
- CVE-2026-86972
- CVE-2026-86969
- CVE-2026-112638
- CVE-2026-112611
- CVE-2026-112610
- CVE-2026-113950
- CVE-2026-86992
- CVE-2026-112706
- CVE-2026-112688
- CVE-2026-86990
- CVE-2026-112656
- CVE-2026-113896
- CVE-2026-112618
- CVE-2026-86970
- CVE-2026-112683
- CVE-2026-112642
- CVE-2026-112432
- CVE-2026-112518
- CVE-2026-112456
- CVE-2026-86978
- CVE-2026-112596
- CVE-2026-112571
- CVE-2026-112561
- CVE-2026-112627
- CVE-2026-112488
- CVE-2026-112634
- CVE-2026-112629
- CVE-2026-112633
- CVE-2026-112614
- CVE-2026-112632
- CVE-2026-112630
- CVE-2026-112625
- CVE-2026-112515
- CVE-2026-65385
- CVE-2026-112459
- CVE-2026-112554
- CVE-2026-112477
- CVE-2026-112576
- CVE-2026-112606
- CVE-2026-65350
- CVE-2026-112679
- CVE-2026-112517
- CVE-2026-112516
- CVE-2026-112514
- CVE-2026-112507
- CVE-2026-84495
- CVE-2026-112474
- CVE-2026-112698
- CVE-2026-112501
- CVE-2026-112476
- CVE-2026-112665
- CVE-2026-112624
- CVE-2026-112522
- CVE-2026-112621
- CVE-2026-112500
- CVE-2026-112671
- CVE-2026-112414
- CVE-2026-112707
- CVE-2026-112607
- CVE-2026-113915
- CVE-2026-112687
- CVE-2026-112682
- CVE-2026-86989
- CVE-2026-112565
- CVE-2026-112449
- CVE-2026-112413
- CVE-2026-112485
- CVE-2026-112461
- CVE-2026-112486
- CVE-2026-65397
- CVE-2026-112676
- CVE-2026-112660
- CVE-2026-112681
- CVE-2026-86925
- CVE-2026-112491
- CVE-2026-112547
- CVE-2026-112609
- CVE-2026-112425
- CVE-2026-112423
- CVE-2026-112464
- CVE-2026-86991
- CVE-2026-112616
- CVE-2026-113913
- CVE-2026-112652
- CVE-2026-112559
- CVE-2026-112455
- CVE-2026-112658
- CVE-2026-112685
- CVE-2022-26704
- CVE-2026-112567
- CVE-2026-112628
- CVE-2026-112646
- CVE-2026-112691
- CVE-2026-86968
- CVE-2026-84605
- CVE-2026-112595
- CVE-2026-112479
- CVE-2026-113904
- CVE-2026-112599
- CVE-2026-86974
- CVE-2026-86986
- CVE-2026-112693
- CVE-2026-86985
- CVE-2026-112699
- CVE-2026-112680
- CVE-2026-112697
- CVE-2026-112655
- CVE-2026-112651
- CVE-2026-112623
- CVE-2026-112686
- CVE-2026-112684
- CVE-2026-112673
- CVE-2026-112669
- CVE-2026-112695
- CVE-2026-112666
- CVE-2026-112654
- CVE-2026-112653
- CVE-2026-112615
- CVE-2026-112659
- CVE-2026-112640
- CVE-2026-113952
- CVE-2026-113949
- CVE-2026-113903
- CVE-2026-112637
- CVE-2026-112626
- CVE-2026-113897
- CVE-2026-112639
- CVE-2026-113901
- CVE-2026-86973
- CVE-2026-113909
- CVE-2026-112622
- CVE-2026-112620
Frequently Asked Questions
What update addresses this issue?
The issue is fixed in iOS 27.2 and iPadOS 27.2. Devices running those versions have the stated fixes.
What level of access does exploitation require?
The supplied severity vector rates the attack vector as local and requires low privileges, with no user interaction. The description also states that a remote attacker may be able to access sensitive user data.