CVE-2025-31217: Input Validation

Published May 12, 2025
·
Updated

afpfs. The issue was addressed with improved memory handling.

Other sources

afpfs. This issue was addressed with improved checks.

Apple

AirDrop. A permissions issue was addressed with additional restrictions.

Apple

Apple Intelligence Reports. A permissions issue was addressed with additional restrictions.

Apple

AppleJPEG. The issue was addressed with improved input sanitization.

Apple

Audio. A double free issue was addressed with improved memory management.

Apple

Credit

Wojciech Regula(SecuRing), Dave G., Kirin@@Pwnrin, 7feilee, Eric Dorphy(Twin Cities App Dev LLC), Adam M., Google V8 Security Team, Ignacio Sanmillan@@ulexec, Jiming Wang, Jikai Ren, an anonymous researcher, Hossein Lotfi@@hosselot(Trend Micro Zero Day Initiative), Guilherme Rambo(Best Buddy Apps), Apple, Google Threat Analysis Group, Saagar Jha, Tony Iskow@@Tybbow, Michael DePlante@@izobashi(Trend Micro Zero Day Initiative), Lucas Leong@@_wmliang_(Trend Micro Zero Day Initiative), Christian Kohlschütter, CVE-2024-8176, Paweł Płatek (Trail(Bits), Andreas Jaegersberger & Ro Achterberg(Nosebeard Labs), wac(Trend Micro Zero Day Initiative), rheza@@ginggilBesel(Palo Alto Networks), Edouard Bochin@@le_douds(Palo Alto Networks), Tao Yan@@Ga1ois(Palo Alto Networks), Nan Wang@@eternalsakura13, Yuhao Hu, Yan Kang, Chenggang Wu, Xiaojie Wei, Ivan Fratric(Google Project Zero), Juergen Schmied(Lynck GmbH), jioundai(360 Vulnerability Research Institute), chen fengjiao(HBC), Ron Masas(BREAKPOINT), Dillon Franke(Google Project Zero), Wang Yu(Cyberserval), Andrew James Gonzalez, Lyutoon(Atredis Partners), YenKoc(Atredis Partners), Dayton Pidhirney(Atredis Partners), Mateusz Krzywicki@@krzywix, Richard Hyunho Im@@richeeta, Andr.Ess, Noah Gregory (wts.dev), wac, Thibaud Kehler, 秦若涵, 崔志伟, 崔宝江, Deval Jariwala, Dalibor Milanovic, YingQi Shi@@Mas0nShi(DBAppSecurity's WeBin lab), Duy Trần@@khanhduytran0, Lyutoon, YenKoc, Shehab Khan, CertiK@@CertiK, @@RenwaX23, Joseph Ravichandran@@0xjprx(MIT CSAIL), Thomas Völkl@@vollkorntomate, SEEMOO, TU Darmstadt, Kirin@@Pwnrin(Fudan University), LFY@@secsys(Fudan University), Bohdan Stasiuk@@bohdan_stasiuk, Sourabhkumar Mishra, CVE-2025-26465, CVE-2025-26466, Csaba Fitzl@@theevilbit(Kandji), Ryan Dowd@@_rdowd

Affected Software

16 affected componentsFixes available
Apple tvOS<18.5
18.5
Apple macOS Sequoia<15.5
15.5
Apple visionOS<2.5
2.5
Apple iPadOS<17.7.7
17.7.7
Apple iOS<18.5
18.5
Apple iPadOS<18.5
18.5
Apple WatchOS<11.5
11.5
Apple Safari<18.5
18.5
Apple Safari<18.5
Apple iPadOS<17.7.7
Apple iPadOS>=18.0<18.5
Apple iPhone OS<18.5
Apple macOS<15.5
Apple tvOS<18.5
Apple visionOS<2.5
Apple WatchOS<11.5

Event History

May 12, 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·09:42 PM
Data Sourced
via MITRE·09:42 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected 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-31217?

The severity of CVE-2025-31217 has been classified as high due to the potential for exploitation leading to unauthorized access.

2

How do I fix CVE-2025-31217?

To fix CVE-2025-31217, update your affected Apple devices to the latest versions listed in the advisory.

3

Which products are affected by CVE-2025-31217?

CVE-2025-31217 affects various Apple products, including tvOS, macOS, iPadOS, visionOS, and watchOS prior to specified versions.

4

What types of vulnerabilities does CVE-2025-31217 address?

CVE-2025-31217 addresses issues related to memory handling, permission checks, and additional restrictions on affected systems.

5

Is there a workaround for CVE-2025-31217?

Currently, no specific workarounds for CVE-2025-31217 are recommended, so applying the update is advised.

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