CVE-2025-43211: Input Validation

Published Jul 29, 2025
·
Updated

Accessibility. A logic issue was addressed with improved checks.

Other sources

Accessibility. The issue was addressed by adding additional logic.

Apple

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

Apple

afclip. The issue was addressed with improved memory handling.

Apple

AMD. A race condition was addressed with improved state handling.

Apple

AppleMobileFileIntegrity. A downgrade issue was addressed with additional code-signing restrictions.

Apple

Credit

Sergei Glazunov(Google Project Zero), Ivan Fratric(Google Project Zero), Andreas Jaegersberger & Ro Achterberg(Nosebeard Labs), Martin Bajanik(Fingerprint), Ammar Askar, Jaydev Ahire, Gilad Moav, Yehuda Afek, Anat Bremler-Barr, Amit Klein, Yuhao Hu, Yan Kang, Chenggang Wu, Xiaojie Wei, Syarif Muhammad Sajjad, shandikri(Trend Micro Zero Day Initiative), Google V8 Security Team, Nan Wang@@eternalsakura13, Ziling Chen, HexRabbit@@h3xr4bb1t(DEVCORE Research Team), Ignacio Sanmillan@@ulexec, Clément Lecigne(Google's Threat Analysis Group), Vlad Stolyarov(Google's Threat Analysis Group), Google's Threat Analysis Group, Hossein Lotfi@@hosselot(Trend Micro Zero Day Initiative), Chi Yuan Chang(ZUSO ART), taikosoup, Gary Kwong(Trend Micro Zero Day Initiative), CVE-2025-43226, Christian Kohlschütter, Michael DePlante@@izobashi(Trend Micro Zero Day Initiative), CVE-2025-6965, Wong Wee Xiang, Himanshu Bharti@@Xpl0itme, Brian Carpenter, Mickey Jin@@patch1t, Dawuge(Shuffle Team), Tony Iskow@@Tybbow, Kirin@@Pwnrin, Wojciech Regula(SecuRing), ABC Research s.r.o., Noah Gregory (wts.dev), MRHAX, Aditya Rana, Seo Hyun-gyu@@wh1te4ever(Xiaomi), Dora Orak(Xiaomi), Minghao Lin@@Y1nKoc(Xiaomi), XiLong Zhang@@Resery4(Xiaomi), noir@@ROIS, fmyy (@风沐云烟), 风沐云烟@@binary_fmyy, Minghao Lin@@Y1nKoc, Gergely Kalman@@gergely_kalman, an anonymous researcher, 2ourc3 | Salim Largo, Anonymous(Trend Micro Zero Day Initiative), Willey Lin, Arsenii Kostromin (0x3c3e), Pyrophoria, Dora Orak, Csaba Fitzl@@theevilbit(Kandji), Minghao Lin, Jiaxun Zhu, Zhongquan Li@@Guluisacat, Koh M. Nakagawa@@tsunek0h(Kandji), an anonymous researcher(Loadshine Lab), Hikerell(Loadshine Lab), @@zlluny, Yuebin Sun@@yuebinsun2020, Shang-De Jiang(CyCraft Technology), Kazma Ye(CyCraft Technology), Nikolai Skliarenko(Trend Micro Zero Day Initiative), Keith Yeo@@kyeojy(Team Orca of Sea Security), Martti Hütt, Jonathan Bar Or@@yo_yo_yo_jbo(Microsoft), Ryan Dowd@@_rdowd

Affected Software

16 affected componentsFixes available
Apple WatchOS<11.6
11.6
Apple macOS Sequoia<15.6
15.6
Apple iOS<18.6
18.6
Apple iPadOS<18.6
18.6
Apple iPadOS<17.7.9
17.7.9
Apple tvOS<18.6
18.6
Apple visionOS<2.6
2.6
Apple Safari<18.6
18.6
Apple Safari<18.6
Apple iPadOS<17.7.9
Apple iPadOS>=18.0<18.6
Apple iPhone OS<18.6
Apple macOS<15.6
Apple tvOS<18.6
Apple visionOS<2.6
Apple WatchOS<11.6

Event History

Jul 29, 2025
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·11:35 PM
Data Sourced
via MITRE·11:35 PM
DescriptionWeakness
Jul 30, 2025
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeaknessAffected Software
Aug 4, 2025
Data Sourced
via Red Hat·12:46 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-43211?

CVE-2025-43211 has been categorized as a high-severity vulnerability due to its potential impact on the affected systems.

2

How do I fix CVE-2025-43211?

To address CVE-2025-43211, users should update their devices to the latest versions as specified in the advisory.

3

Which software is affected by CVE-2025-43211?

CVE-2025-43211 affects multiple Apple products including watchOS versions up to 11.6 and macOS Sequoia versions up to 15.6.

4

Is there a workaround for CVE-2025-43211?

No official workarounds are provided for CVE-2025-43211; the best practice is to apply the recommended updates.

5

What type of vulnerability is CVE-2025-43211?

CVE-2025-43211 is primarily a logic issue that has been addressed with improved validation and memory handling.

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