CVE-2026-20605: Buffer Overflow

Published Feb 11, 2026
·
Updated

Accessibility. An inconsistent user interface issue was addressed with improved state management.

Other sources

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

— Apple

App Intents. A logic issue was addressed with improved restrictions.

— 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

Wong Wee Xiang, Loh Boon Keat, piffz, Daniel Nurkin, Al Sadman Awal, Mohamed Hamdadou & Mahran Alhazmi, Hichem Maloufi, Christian Mina, Gerson Aldaz, qwerty j0y & Ricardo Garcia, Dorian Del Valle, Amy (amys.website), Anonymous(Trend Micro Zero Day Initiative), Yiğit Can YILMAZ@@yilmazcanyigit, George Karchemsky@@gkarchemsky(Trend Micro Zero Day Initiative), 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, an anonymous researcher, Ron Masas(BreakPoint), Michael DePlante@@izobashi(Trend Micro Zero Day Initiative), Google Threat Analysis Group, Mickey Jin@@patch1t, Noah Gregory (wts.dev), Óscar García Pérez, Stanislav Jelezoglo, Viktor Lord Härringtón, Enis Maholli (enismaholli.com), Gongyu Ma@@Mezone0, LeminLimez, @@cloudlldb, Dalibor Milanovic, HanQing(TSDubhe), Nan Wang@@eternalsakura13, Nathaniel Oh@@calysteon, EntryHi, Wang Yu(Cyberserval), jioundai, Kirin@@Pwnrin(Fudan University), LFY@@secsys(Fudan University), Golden Helm Securities(Iru), Gergely Kalman@@gergely_kalman(Iru), Csaba Fitzl@@theevilbit(Iru), Gergely Kalman@@gergely_kalman, Kirin@@Pwnrin, Asaf Cohen, Murray Mike, Jian Lee@@speedyfriend433, Keisuke Hosoda, Chunyu Song(NorthSea), Rodolphe Brunetti@@eisw0lf(Lupus Nova), Pwn2car, CVE-2026-20622, Morris Richman@@morrisinlife, Vivek Dhar, ASI (RM) in Border Security Force, FTR HQ BSF Kashmir, Tom Van Goethem, Ryan Dowd@@_rdowd, Johnny Franks (zeroxjf), Ron Elemans, Kenneth Chew, Bing Shi(Alibaba Group), Wenchao Li(Alibaba Group), Xiaolong Bai(Alibaba Group), (Indiana University Bloomington), Luyi Xing(Indiana University Bloomington), Vamshi Paili, Tony Gorez for Reverse Society@@tonygo_, 이동하 (Lee Dong Ha)(SSA Lab)

Affected Software

10 affected componentsFixes available
Apple macOS Sequoia<15.7.4
15.7.4
Apple macOS Tahoe<26.3
26.3
Apple iOS<18.7.5
18.7.5
Apple iPadOS<18.7.5
18.7.5
Apple macOS Sonoma<14.8.4
14.8.4
Apple iPadOS<18.7.5
Apple iPhone OS<18.7.5
Apple macOS>=14.0<14.8.4
Apple macOS>=15.0<15.7.4
Apple macOS>=26.0<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 18.7.5
  2. Upgrade

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

    Fixed in 15.7.4
  3. Upgrade

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

    Fixed in 26.3
  4. Upgrade

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

    Fixed in 14.8.4
  5. Upgrade

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

    Fixed in iOS 18.7.5
  6. Upgrade

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

    Fixed in iPadOS 18.7.5
  7. Upgrade

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

    Fixed in macOS Sequoia 15.7.4
  8. Upgrade

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

    Fixed in macOS Sonoma 14.8.4
  9. Upgrade

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

    Fixed in macOS Tahoe 26.3
  10. Remove

    Remove the affected component from your environment.

    This issue was addressed by blocking the vulnerable package (PackageKit). Block the vulnerable package using PackageKit so it cannot be installed/used.

  11. Remove

    Remove the affected component from your environment.

    This issue was addressed by removing the vulnerable code; remove/uninstall the vulnerable code component(s) in the affected area.

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
Description
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionAffected Software
CVE Published
via MITRE·10:59 PM
Data Sourced
via MITRE·10:59 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
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-20605?

The severity of CVE-2026-20605 is classified as a moderate risk due to the potential impacts of the parsing issues.

2

How do I fix CVE-2026-20605?

To address CVE-2026-20605, users should update to the latest version of macOS Sequoia, macOS Tahoe, iOS, iPadOS, or macOS Sonoma as appropriate.

3

What products are impacted by CVE-2026-20605?

CVE-2026-20605 affects macOS Sequoia, macOS Tahoe, iOS, iPadOS, and macOS Sonoma up to specified versions.

4

What kind of issues does CVE-2026-20605 address?

CVE-2026-20605 addresses parsing issues in handling directory paths and inconsistent user interface problems.

5

Who is vulnerable to CVE-2026-20605?

Users running the specified versions of affected Apple operating systems are vulnerable to CVE-2026-20605.

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