CVE-2026-84618: Input Validation
A permissions issue was addressed with improved validation. This issue is fixed in macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7. An app may be able to access sensitive user data.
Other sources
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. An authorization issue was addressed with improved state management.
— Apple
APFS. A permissions issue was addressed with improved path validation.
— Apple
APFS. An out-of-bounds write issue was addressed with improved bounds checking.
— 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 27 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 26.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.8 - Upgrade
Upgrade
macOS Golden Gateto a version that resolves this vulnerability.Fixed in 27 - 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.7 - Compensating control
Where the issue involves an access/sandboxing risk for system pasteboards, apply the additional sandbox restrictions on the system pasteboards as described in the fix.
- Compensating control
Where the issue involves authorization/access, apply the improved access control/state management/entitlement checks as described in the fix (e.g., additional entitlement checks and improved validation of the process entitlement).
- Operational
After upgrading to the fixed macOS versions, ensure affected components/workflows are revalidated because the issue categories include memory corruption and logic/validation flaws addressed by code changes.
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-86882
- CVE-2026-43664
- CVE-2026-65404
- CVE-2026-86910
- CVE-2026-84523
- CVE-2026-86888
- CVE-2026-84587
- CVE-2026-84586
- CVE-2026-20683
- CVE-2026-84601
- CVE-2026-65408
- CVE-2026-65407
- CVE-2026-84519
- CVE-2026-84520
- CVE-2026-65381
- CVE-2026-84584
- CVE-2026-84522
- CVE-2026-84525
- CVE-2026-65342
- CVE-2026-86905
- CVE-2026-84583
- CVE-2026-84570
- CVE-2026-84568
- CVE-2026-84535
- CVE-2026-65410
- CVE-2026-84616
- CVE-2026-84607
- CVE-2026-65406
- CVE-2026-65414
- CVE-2026-84560
- CVE-2026-84631
- CVE-2026-84567
- CVE-2026-65399
- CVE-2026-86891
- CVE-2026-43683
- CVE-2026-43789
- CVE-2026-64752
- CVE-2026-86876
- CVE-2026-65344
- CVE-2026-84624
- CVE-2026-43737
- CVE-2026-84574
- CVE-2026-84559
- CVE-2026-43786
- CVE-2026-65412
- CVE-2026-84596
- CVE-2026-84575
- CVE-2026-84489
- CVE-2026-84571
- CVE-2026-43738
- CVE-2026-84511
- CVE-2026-84563
- CVE-2026-34979
- CVE-2026-43698
- CVE-2026-64790
- CVE-2026-43692
- CVE-2026-84554
- CVE-2026-43691
- CVE-2026-84541
- CVE-2026-84540
- CVE-2026-84516
- CVE-2026-84612
- CVE-2026-84505
- CVE-2026-84565
- CVE-2026-84552
- CVE-2026-84550
- CVE-2026-65362
- CVE-2026-84512
- CVE-2026-84510
- CVE-2026-86901
- CVE-2026-86900
- CVE-2026-43785
- CVE-2026-84534
- CVE-2026-43688
- CVE-2026-84524
- CVE-2026-84597
- CVE-2026-84569
- CVE-2026-65409
- CVE-2026-86911
- CVE-2026-84618
- CVE-2026-84492
- CVE-2026-84533
- CVE-2022-3437
- CVE-2026-84581
- CVE-2026-28934
- CVE-2026-84606
- CVE-2026-64756
- CVE-2026-64714
- CVE-2026-84564
- CVE-2026-86869
- CVE-2026-65395
- CVE-2026-28969
- CVE-2026-65398
- CVE-2026-64760
- CVE-2026-65354
- CVE-2026-84588
- CVE-2026-28968
- CVE-2026-84566
- CVE-2026-65415
- CVE-2026-84561
- CVE-2026-84630
- CVE-2026-65401
- CVE-2026-65360
- CVE-2026-65358
- CVE-2026-84558
- CVE-2026-65377
- CVE-2026-84622
- CVE-2026-84549
- CVE-2026-43689
- CVE-2026-84619
- CVE-2026-65369
- CVE-2026-86917
- CVE-2026-84544
- CVE-2026-43790
- CVE-2026-43687
- CVE-2026-43686
- CVE-2026-84538
- CVE-2026-43684
- CVE-2026-65405
- CVE-2026-65364
- CVE-2026-84530
- CVE-2026-84521
- CVE-2026-65402
- CVE-2026-65359
- CVE-2026-84517
- CVE-2026-84507
- CVE-2026-86903
- CVE-2026-84602
- CVE-2026-84514
- CVE-2026-84556
- CVE-2026-65382
- CVE-2026-86870
- CVE-2026-86894
- CVE-2026-84577
- CVE-2026-84573
- CVE-2026-43787
- CVE-2026-84628
- CVE-2026-43741
- CVE-2026-86924
- CVE-2026-84497
- CVE-2026-84585
- CVE-2026-43695
- CVE-2026-84626
- CVE-2026-86902
- CVE-2026-64712
- CVE-2026-84491
- CVE-2026-84580
- CVE-2026-84578
- CVE-2026-84576
- CVE-2026-84548
- CVE-2026-28966
- CVE-2026-84532
- CVE-2026-65403
- CVE-2026-84518
- CVE-2026-86897
- CVE-2026-65380
- CVE-2026-84555
- CVE-2026-84551
- CVE-2026-84625
- CVE-2026-43697
- CVE-2026-84487
- CVE-2026-65413
- CVE-2026-84632
- CVE-2026-84620
- CVE-2026-84546
- CVE-2026-84611
- CVE-2026-84526
- CVE-2026-65400
- CVE-2026-86889
- CVE-2026-86881
- CVE-2026-84531
- CVE-2026-84600
- CVE-2026-86884
- CVE-2026-43690
- CVE-2026-43719
- CVE-2026-65376
- CVE-2026-84543
- CVE-2026-84537
- CVE-2026-84536
- CVE-2026-65365
- CVE-2026-84515
- CVE-2026-84509
- CVE-2026-84553
- CVE-2026-84609
- CVE-2026-65361
- CVE-2026-65378
- CVE-2026-84621
- CVE-2026-43788
- CVE-2026-65348
- CVE-2026-65345
- CVE-2026-43791
- CVE-2026-84513
- CVE-2026-65383
- CVE-2026-86909
- CVE-2026-84527
- CVE-2026-84589
- CVE-2026-28937
- CVE-2026-43696
- CVE-2026-84572
- CVE-2026-84506
- CVE-2026-28899
- CVE-2026-65374
- CVE-2026-65375
- CVE-2026-43677
- CVE-2026-84635
- CVE-2026-64753
- CVE-2026-86898
- CVE-2026-64718
- CVE-2026-65393
- CVE-2026-84617
- CVE-2026-43763
- CVE-2026-43702
- CVE-2026-43743
- CVE-2026-43760
- CVE-2026-65339
- CVE-2026-64758
- CVE-2026-65346
- CVE-2026-64736
- CVE-2026-65349
- CVE-2026-65330
- CVE-2026-28935
- CVE-2026-65371
- CVE-2026-28930
Frequently Asked Questions
What access does an attacker need to exploit this issue?
The CVSS vector indicates local access and user interaction are required. The attacker does not need privileges.
What is the expected impact if exploitation succeeds?
The CVSS assessment indicates a high confidentiality impact, with no integrity or availability impact listed. The description states that an app may be able to access sensitive user data.
Which macOS releases include the fix?
The issue is fixed in macOS Golden Gate 27, macOS Sequoia 15.8, and macOS Tahoe 26.7. Updating to the applicable fixed release is the remediation identified in the provided data.