CVE-2026-20627: Use After Free
Accessibility. A privacy issue was addressed by removing sensitive data.
Other sources
Accessibility. An inconsistent user interface issue was addressed with improved state management.
— Apple
Admin Framework. A parsing issue in the handling of directory paths was addressed with improved path validation.
— Apple
An issue existed in the handling of environment variables. This issue was addressed with improved validation. This issue is fixed in iOS 26.3 and iPadOS 26.3, macOS Sonoma 14.8.4, macOS Tahoe 26.3, visionOS 26.3, watchOS 26.3. An app may be able to access sensitive user data.
— MITRE
AppleEvents. An authorization issue was addressed with improved state management.
— Apple
AppleKeyStore. A use after free issue was addressed with improved memory management.
— Apple
Credit
Affected Software
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-20637
- CVE-2026-20650
- CVE-2026-20611
- CVE-2026-20609
- CVE-2026-20617
- CVE-2026-20627
- CVE-2025-14174
- CVE-2025-43529
- CVE-2026-20700
- CVE-2026-20649
- CVE-2026-20675
- CVE-2026-20634
- CVE-2026-20654
- CVE-2026-20671
- CVE-2025-59375
- CVE-2026-20667
- CVE-2026-20628
- CVE-2026-20641
- CVE-2026-20635
- CVE-2026-20645
- CVE-2026-20674
- CVE-2026-20638
- CVE-2026-20660
- CVE-2026-20686
- CVE-2026-20615
- CVE-2026-20668
- CVE-2026-20626
- CVE-2026-20663
- CVE-2026-20655
- CVE-2026-20677
- CVE-2026-20694
- CVE-2026-20642
- CVE-2026-20678
- CVE-2026-28855
- CVE-2026-20682
- CVE-2026-20653
- CVE-2026-20680
- CVE-2026-20606
- CVE-2026-20640
- CVE-2026-20661
- CVE-2026-20652
- CVE-2026-20608
- CVE-2026-20676
- CVE-2026-20644
- CVE-2026-20636
- CVE-2026-20621
- CVE-2026-20670
- CVE-2026-20624
- CVE-2026-20625
- CVE-2025-43403
- CVE-2025-46283
- CVE-2025-43417
- CVE-2026-20620
- CVE-2025-43338
- CVE-2026-20673
- CVE-2026-20651
- CVE-2026-20616
- CVE-2025-43533
- CVE-2025-46300
- CVE-2025-46301
- CVE-2025-46302
- CVE-2025-46303
- CVE-2025-46304
- CVE-2025-46305
- CVE-2025-46310
- CVE-2026-20614
- CVE-2025-46290
- CVE-2026-20612
- CVE-2026-20605
- CVE-2025-43402
- CVE-2026-20602
- CVE-2026-20669
- CVE-2026-20639
- CVE-2026-20681
- CVE-2026-20629
- CVE-2026-20601
- CVE-2026-20623
- CVE-2026-20630
- CVE-2026-20603
- CVE-2026-20666
- CVE-2026-20656
- CVE-2026-20658
- CVE-2026-20610
- CVE-2026-20622
- CVE-2026-20648
- CVE-2026-20662
- CVE-2026-20647
- CVE-2026-20699
- CVE-2026-20619
- CVE-2026-20618
- CVE-2026-20646
Frequently Asked Questions
What is the severity of CVE-2026-20627?
CVE-2026-20627 is classified as a moderate severity vulnerability affecting several Apple operating systems.
How do I fix CVE-2026-20627?
To remediate CVE-2026-20627, update your devices to the latest software version beyond the affected versions.
What types of devices are affected by CVE-2026-20627?
CVE-2026-20627 affects Apple devices running visionOS, iOS, iPadOS, macOS Tahoe, macOS Sonoma, and watchOS version up to exclusive 26.3 or 14.8.4.
What kind of issues does CVE-2026-20627 address?
CVE-2026-20627 addresses issues related to privacy, user interface inconsistencies, and directory path parsing.
Is CVE-2026-20627 relevant to enterprise environments?
Yes, CVE-2026-20627 can impact enterprise environments utilizing the affected Apple operating systems, necessitating swift action to mitigate the risk.