CVE-2026-65339: Use After Free
A logic issue was addressed with improved checks. This issue is fixed in iOS 18.7.11 and iPadOS 18.7.11, iOS 26.6.1 and iPadOS 26.6.1, macOS Sequoia 15.8, macOS Tahoe 26.6.2, tvOS 27, visionOS 27, watchOS 27. An app may be able to leak sensitive user information.
Other sources
A logic issue was addressed with improved checks. This issue is fixed in iOS 26.6.1 and iPadOS 26.6.1, macOS Sequoia 15.8, macOS Tahoe 26.6.2, tvOS 27, visionOS 27, watchOS 27. An app may be able to leak sensitive user information.
— NVD
Accelerate Framework. An out-of-bounds write issue was addressed with improved bounds checking.
— Apple
Accessibility. This issue was addressed with improved data protection.
— Apple
Accounts. This issue was addressed with additional entitlement checks.
— Apple
AMD. The issue was addressed with improved checks.
— Apple
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 26.6.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 26.6.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 27 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 18.7.11 - Upgrade
Upgrade
iOS/iPadOSto a version that resolves this vulnerability.Fixed in 18.7.11 - Upgrade
Upgrade
iOS/iPadOSto a version that resolves this vulnerability.Fixed in 26.6.1 - Upgrade
Upgrade
macOS Sequoiato a version that resolves this vulnerability.Fixed in 15.8 - Upgrade
Upgrade
macOS Tahoeto a version that resolves this vulnerability.Fixed in 26.6.2 - Upgrade
Upgrade
tvOSto a version that resolves this vulnerability.Fixed in 27 - Upgrade
Upgrade
visionOSto a version that resolves this vulnerability.Fixed in 27 - Upgrade
Upgrade
watchOSto a version that resolves this vulnerability.Fixed in 27
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-65339
- CVE-2026-65355
- CVE-2026-65347
- CVE-2026-65346
- CVE-2026-64788
- CVE-2026-64736
- CVE-2026-65343
- CVE-2026-65349
- CVE-2026-65330
- CVE-2026-28935
- CVE-2026-64784
- CVE-2026-43795
- CVE-2026-65338
- CVE-2026-65341
- CVE-2026-64782
- CVE-2026-64781
- CVE-2026-65351
- CVE-2026-65340
- CVE-2026-65337
- CVE-2026-65336
- CVE-2026-65335
- CVE-2026-65333
- CVE-2026-65332
- CVE-2026-65331
- CVE-2026-64715
- CVE-2026-64780
- CVE-2026-65334
- CVE-2026-43794
- CVE-2026-64787
- CVE-2026-65352
- CVE-2026-64778
- CVE-2026-64779
- CVE-2026-65391
- CVE-2026-65390
- CVE-2026-65329
- CVE-2026-86950
- CVE-2026-86990
- CVE-2026-86882
- CVE-2026-86918
- CVE-2026-43664
- CVE-2026-84523
- CVE-2026-86888
- CVE-2026-84582
- CVE-2026-84586
- CVE-2026-65407
- CVE-2026-84583
- CVE-2026-65410
- CVE-2026-84616
- CVE-2026-84607
- CVE-2026-65414
- CVE-2026-84560
- CVE-2026-84613
- CVE-2026-86895
- CVE-2026-86893
- CVE-2026-65399
- CVE-2026-86891
- CVE-2026-112608
- CVE-2026-86876
- CVE-2026-86913
- CVE-2026-43737
- CVE-2026-65412
- CVE-2026-84596
- CVE-2026-84575
- CVE-2026-84571
- CVE-2026-84511
- CVE-2026-84612
- CVE-2026-84524
- CVE-2026-84597
- CVE-2026-65409
- CVE-2026-84492
- CVE-2026-84533
- CVE-2026-84564
- CVE-2026-86975
- CVE-2026-86954
- CVE-2026-28969
- CVE-2026-65398
- CVE-2026-64760
- CVE-2026-28968
- CVE-2026-65415
- CVE-2026-84561
- CVE-2026-84630
- CVE-2026-65360
- CVE-2026-65358
- CVE-2026-65377
- CVE-2026-84622
- CVE-2026-43687
- CVE-2026-43686
- CVE-2026-65405
- CVE-2026-84530
- CVE-2026-65402
- CVE-2026-65359
- CVE-2026-84507
- CVE-2026-86903
- CVE-2026-84599
- CVE-2026-84602
- CVE-2026-86962
- CVE-2026-86964
- CVE-2026-86870
- CVE-2026-84628
- CVE-2026-43695
- CVE-2026-84626
- CVE-2026-84491
- CVE-2026-84629
- CVE-2026-65403
- CVE-2026-84551
- CVE-2026-84625
- CVE-2026-84603
- CVE-2026-84487
- CVE-2026-84632
- CVE-2026-84620
- CVE-2026-84546
- CVE-2026-84611
- CVE-2026-84526
- CVE-2026-86881
- CVE-2026-84600
- CVE-2026-86884
- CVE-2026-84609
- CVE-2026-84513
- CVE-2026-86886
- CVE-2026-84527
- CVE-2026-86904
- CVE-2026-84635
- CVE-2026-64753
- CVE-2026-86872
- CVE-2026-86953
- CVE-2026-86957
- CVE-2026-84636
- CVE-2026-65406
- CVE-2026-65344
- CVE-2026-43785
- CVE-2026-65395
- CVE-2026-84497
- CVE-2026-84615
- CVE-2026-28966
- CVE-2026-84532
- CVE-2026-84617
- CVE-2026-20683
- CVE-2026-86920
- CVE-2026-84634
- CVE-2026-84595
- CVE-2026-86905
- CVE-2026-86966
- CVE-2026-86919
- CVE-2026-64752
- CVE-2026-84624
- CVE-2026-84534
- CVE-2026-86942
- CVE-2026-84606
- CVE-2026-43689
- CVE-2026-84521
- CVE-2026-86883
- CVE-2026-65411
- CVE-2026-84627
- CVE-2026-86897
- CVE-2026-84508
- CVE-2026-28850
- CVE-2026-86921
- CVE-2026-86892
- CVE-2026-86887
- CVE-2026-86898
- CVE-2026-86922
- CVE-2026-64718
- CVE-2026-112446
- CVE-2026-28853
- CVE-2026-86910
- CVE-2026-65396
- CVE-2026-84587
- CVE-2026-65408
- CVE-2026-84519
- CVE-2026-65381
- CVE-2026-43763
- CVE-2026-84525
- CVE-2026-65342
- CVE-2026-84568
- CVE-2026-84570
- CVE-2026-84535
- CVE-2026-84547
- CVE-2026-84567
- CVE-2026-86907
- CVE-2026-43683
- CVE-2026-43789
- CVE-2026-43702
- CVE-2026-84574
- CVE-2026-84559
- CVE-2026-43786
- CVE-2026-84563
- CVE-2026-84540
- CVE-2026-84554
- CVE-2026-43692
- CVE-2026-64790
- CVE-2026-43691
- CVE-2026-84516
- CVE-2026-84541
- CVE-2026-84579
- CVE-2026-84505
- CVE-2026-84565
- CVE-2026-84552
- CVE-2026-84550
- CVE-2026-65362
- CVE-2026-84512
- CVE-2026-84510
- CVE-2026-84618
- CVE-2026-86981
- CVE-2022-3437
- CVE-2026-86868
- CVE-2026-28934
- CVE-2026-84581
- CVE-2026-64756
- CVE-2026-64758
- CVE-2026-64759
- CVE-2026-86944
- CVE-2026-84566
- CVE-2026-84619
- CVE-2026-84549
- CVE-2026-43790
- CVE-2026-65369
- CVE-2026-84544
- CVE-2026-86917
- CVE-2026-43684
- CVE-2026-84538
- CVE-2026-65364
- CVE-2026-84517
- CVE-2026-65371
- CVE-2019-5598
- CVE-2026-86916
- CVE-2026-84514
- CVE-2026-84556
- CVE-2026-65382
- CVE-2026-84573
- CVE-2026-43787
- CVE-2026-86914
- CVE-2026-43741
- CVE-2026-86959
- CVE-2026-65372
- CVE-2026-64712
- CVE-2026-84580
- CVE-2026-84578
- CVE-2026-84576
- CVE-2026-84548
- CVE-2026-84555
- CVE-2026-65413
- CVE-2026-43697
- CVE-2026-86889
- CVE-2026-65356
- CVE-2026-43719
- CVE-2026-43690
- CVE-2026-65376
- CVE-2026-84543
- CVE-2026-84536
- CVE-2026-84537
- CVE-2026-65365
- CVE-2026-84515
- CVE-2026-84509
- CVE-2026-86871
- CVE-2026-84553
- CVE-2026-65361
- CVE-2026-28930
- CVE-2026-65378
- CVE-2026-84621
- CVE-2026-65345
- CVE-2026-65348
- CVE-2026-43791
- CVE-2026-84572
- CVE-2026-84506
- CVE-2026-43677
- CVE-2026-65375
- CVE-2026-65374
- CVE-2026-28899
- CVE-2026-65379
Frequently Asked Questions
Which systems should be prioritized for remediation?
The issue affects Apple iOS, iPadOS, and macOS Tahoe systems that have not installed the listed fixes: iOS 26.6.1, iPadOS 26.6.1, or macOS Tahoe 26.6.2.
What access would an attacker need, and what is the likely impact?
Exploitation requires local access, low privileges, and user interaction according to the CVSS vector. A successful exploit may allow an app to disclose sensitive user information; integrity and availability impact are not indicated.
What should teams do if they are affected?
Install iOS 26.6.1, iPadOS 26.6.1, or macOS Tahoe 26.6.2, as applicable. The provided information does not identify a workaround or mitigation for systems that cannot yet be updated.