CVE-2026-20636: Use After Free

Published Feb 11, 2026
·
Updated

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

AppleEvents. An authorization issue was addressed with improved state management.

— Apple

AppleKeyStore. A use after free issue was addressed with improved memory management.

— Apple

AppleMobileFileIntegrity. A parsing issue in the handling of directory paths was addressed with improved path validation.

— Apple

Credit

Amy (amys.website), Mickey Jin@@patch1t, Nathaniel Oh@@calysteon, HanQing(TSDubhe), Nan Wang@@eternalsakura13, Tom Van Goethem, EntryHi, Wong Wee Xiang, Loh Boon Keat, Jacob Prezant (prezant.us), Johnny Franks (zeroxjf), an anonymous researcher, jioundai, Nils Hanff @chaos.social)@@nils1729(Hasso Plattner Institute), Atul Kishor Jaiswal, Anonymous(Trend Micro Zero Day Initiative), Yiğit Can YILMAZ@@yilmazcanyigit, Golden Helm Securities(Iru), Gergely Kalman@@gergely_kalman(Iru), Csaba Fitzl@@theevilbit(Iru), Gergely Kalman@@gergely_kalman, Google Threat Analysis Group, Kirin@@Pwnrin, Asaf Cohen, George Karchemsky@@gkarchemsky(Trend Micro Zero Day Initiative), Jian Lee@@speedyfriend433, Keisuke Hosoda, Xin'an Zhou, Juefei Pu, Zhutian Liu, Zhiyun Qian, Zhaowei Tan, Srikanth V. Krishnamurthy, Mathy Vanhoef, Zhongcheng Li(IES Red Team), CVE-2025-59375, Richard Hyunho Im at Route Zero Security (routezero.security)@@richeeta, Ron Masas(BreakPoint), Rodolphe Brunetti@@eisw0lf(Lupus Nova), Dalibor Milanovic, Noah Gregory (wts.dev), Óscar García Pérez, Stanislav Jelezoglo, Viktor Lord Härringtón, Enis Maholli (enismaholli.com), Gongyu Ma@@Mezone0, LeminLimez, Wang Yu(Cyberserval), Michael DePlante@@izobashi(Trend Micro Zero Day Initiative), Ryan Dowd@@_rdowd, @@cloudlldb, Kirin@@Pwnrin(Fudan University), LFY@@secsys(Fudan University), Murray Mike, Chunyu Song(NorthSea), Pwn2car, CVE-2026-20622, Morris Richman@@morrisinlife, Vivek Dhar, ASI (RM) in Border Security Force, FTR HQ BSF Kashmir

Affected Software

10 affected componentsFixes available
Apple visionOS<26.3
26.3
Apple iOS<26.3
26.3
Apple iPadOS<26.3
26.3
Apple macOS Tahoe<26.3
26.3
Apple Safari<26.3
26.3
Apple Safari<26.3
Apple iPadOS<26.3
Apple iPhone OS<26.3
Apple macOS<26.3
Apple visionOS<26.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 26.3
  2. Remove

    Remove vulnerable code from your environment.

    Remove the vulnerable code as part of the fix described in the material.

Event History

Feb 11, 2026
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeakness
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
Affected Software
CVE Published
via MITRE·10:58 PM
Data Sourced
via MITRE·10:58 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeaknessAffected Software
Mar 18, 2026
Data Sourced
via Red Hat·08:20 PM
DescriptionSeverityAffected Software
Jan 23, 58467
Event
via NVD·04:51 PM

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-20636?

CVE-2026-20636 is classified as a moderate severity vulnerability affecting several Apple products.

2

How do I fix CVE-2026-20636?

To fix CVE-2026-20636, update your software to the latest version 26.3 or later for affected Apple products.

3

Which products are affected by CVE-2026-20636?

CVE-2026-20636 affects Apple visionOS, iOS, iPadOS, macOS Tahoe, and Safari versions up to 26.3.

4

What type of vulnerabilities are addressed in CVE-2026-20636?

CVE-2026-20636 addresses a privacy issue and improves state management in user interfaces and path validation.

5

What are the potential risks of not addressing CVE-2026-20636?

Not addressing CVE-2026-20636 may expose sensitive data and lead to inconsistent user interface behavior or path handling issues.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203