CVE-2026-20632: Use After Free

Published Mar 24, 2026
·
Updated

802.1X. An authentication issue was addressed with improved state management.

Other sources

A parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in macOS Tahoe 26.4. An app may be able to access sensitive user data.

— NVD

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

— Apple

Admin Framework. A path handling issue was addressed with improved validation.

— Apple

apache. This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.

— Apple

AppleMobileFileIntegrity. A downgrade issue affecting Intel-based Mac computers was addressed with additional code-signing restrictions.

— Apple

Credit

Rosyna Keller(Totally Not Malicious Software), Ryan Dowd@@_rdowd, CVE-2025-55753, CVE-2025-58098, CVE-2025-59775, CVE-2025-65082, CVE-2025-66200, Mickey Jin@@patch1t, an anonymous researcher, Koh M. Nakagawa@@tsunek0h(FFRI Security Inc), Talal Haj Bakry(Mysk Inc), Tommy Mysk@@mysk_co(Mysk Inc), Zhongquan Li@@Guluisacat, Justin Cohen(Google), Jex Amro, Cristian Dinca (icmd.tech), Hossein Lotfi@@hosselot(TrendAI Zero Day Initiative), YingQi Shi@@Mas0nShi(DBAppSecurity's WeBin lab), Mustafa Calap@@ordinal0, dbg.re), Etienne Charron (Renault), Victoria Martini (Renault), Zhongcheng Li(IES Red Team), Andreas Jaegersberger & Ro Achterberg(Nosebeard Labs), Asaf Cohen, CVE-2025-14524, 风沐云烟@@binary_fmyy, Minghao Lin@@Y1nKoc, Jonathan Bar Or@@yo_yo_yo_jbo, DARKNAVY@@DarkNavyOrg, XiguaSec, Ye Zhang(Baidu Security), Ryan Dowd@@_rdowd(Iru), Csaba Fitzl@@theevilbit(Iru), CVE-2025-64505, Joseph Ravichandran@@0xjprx(MIT CSAIL), Gor Aleksanyan(BoB 0xB6), Dhiyanesh Selvaraj@@redroot97(BoB 0xB6), 이동하 (Lee Dong Ha(BoB 0xB6), Jian Lee@@speedyfriend433, hari shanmugam, Johnny Franks@@0xjohnny, Yuebin Sun@@yuebinsun2020(SecuRing), an anonymous researcher(SecuRing), Nathaniel Oh@@calysteon(SecuRing), Kirin@@Pwnrin(SecuRing), Wojciech Regula(SecuRing), Joshua Jewett@@JoshJewett33, Ilya Andr (andrd3v)(RTU MIREA), Ilias Morad (A2nkF)(Voynich Group), Duy Trần@@khanhduytran0, @@hugeBlack, Himanshu Bharti@@Xpl0itme(Khatima), Rodolphe Brunetti@@eisw0lf(Lupus Nova), Matej Moravec@@MacejkoMoravec, Dawuge(Shuffle Team), Hunan University, Gergely Kalman@@gergely_kalman, Andrei Dodu, Morris Richman@@morrisinlife, Kun Peeks@@SwayZGl1tZyyy, Dave G., Gyujeong Jin at Team.0xb6@@G1uN4sh, wdszzml, Atuin Automated Vulnerability Discovery Engine, Alex Radocea, Christian Kohlschütter, Sreejith Krishnan R, @@pixiepointsec, Luke Roberts@@rookuu, Pedro Tôrres@@t0rr3sp3dr0, Caspian Tarafdar, Andrew Becker, webb, Thomas Espach, @@hamayanhamayan, Yeonghyeon Choi, Daniel Rhea, Söhnke Benedikt Fischedick (Tripton), Emrovsky & Switch3301, Yevhen Pervushyn, Minse Kim, Narcis Oliveras Fontàs, Nathaniel Oh@@calysteon, Hongze Wu(Ant Group Infrastructure Security Team), Shuaike Dong(Ant Group Infrastructure Security Team), greenbynox, Arni Hardarson, Gongyu Ma@@Mezone0, Héloïse Gollier, Mathy Vanhoef (KU Leuven)

Affected Software

2 affected componentsFixes available
Apple macOS Tahoe<26.4
26.4
Apple macOS>=26.0<26.4

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.4
  2. Upgrade

    Upgrade macOS to a version that resolves this vulnerability.

    Fixed in 26.4
  3. Configuration

    Remove the vulnerable code to address the permissions issue described as being addressed by removing the vulnerable code.

    Permissions (affected subsystem code) remove vulnerable code = enabled
  4. Configuration

    Apply the additional permissions restrictions described in the material to address the permissions issue.

    Permissions (affected subsystem) add restrictions = enabled
  5. Configuration

    Apply the additional sandbox restrictions described in the material to address the permissions issue.

    Permissions (affected subsystem) add sandbox restrictions = enabled
  6. Configuration

    Address the privacy issue by moving sensitive data, as described in the material.

    Privacy (affected data handling) move sensitive data = as instructed
  7. Configuration

    Address the privacy issue by removing sensitive data, as described in the material.

    Privacy (affected data handling) remove sensitive data = as instructed
  8. Configuration

    Address the privacy issue by improving handling of temporary files, as described in the material.

    Privacy (temporary file handling) improve temporary file handling = as instructed
  9. Configuration

    Address the privacy issue by improving handling of user preferences, as described in the material.

    Privacy (user preferences handling) improve user preferences handling = as instructed
  10. Configuration

    Update to include improved handling of symlinks and improved permissions checking and improved validation of symlinks, as described in the material.

    Apple symlink handling improve validation/permissions checks = as instructed

Event History

Mar 24, 2026
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeakness
Updated
via Apple·12:00 AM
Description
Mar 25, 2026
CVE Published
via MITRE·12:32 AM
Data Sourced
via MITRE·12:32 AM
DescriptionWeakness
Data Sourced
via NVD·01:17 AM
DescriptionSeverityWeaknessAffected Software

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-20632?

The severity of CVE-2026-20632 is medium with a CVSS score of 5.3.

2

How do I fix CVE-2026-20632?

To fix CVE-2026-20632, update to macOS Tahoe 26.4 or later.

3

What type of issue is addressed in CVE-2026-20632?

CVE-2026-20632 addresses an authentication issue with improved state management for 802.1X.

4

What vulnerabilities are associated with CVE-2026-20632?

CVE-2026-20632 is associated with risks such as Use After Free, Input Validation, Null Pointer Dereference, Race Condition, and Buffer Overflow.

5

Can an app exploit CVE-2026-20632 to access user data?

Yes, an app may be able to access sensitive user data due to the vulnerabilities in CVE-2026-20632.

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