CVE-2025-31233: Use After Free

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

Hossein Lotfi@@hosselot(Trend Micro Zero Day Initiative), Csaba Fitzl@@theevilbit(Kandji), an anonymous researcher, Dayton Pidhirney(Atredis Partners), Lyutoon, YenKoc, Mateusz Krzywicki@@krzywix, 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), LFY@@secsys(Fudan University), wac, Dave G., Kirin@@Pwnrin, 7feilee, Eric Dorphy(Twin Cities App Dev LLC), Adam M., Lyutoon(Atredis Partners), YenKoc(Atredis Partners), CVE-2025-26465, CVE-2025-26466, Joseph Ravichandran@@0xjprx(MIT CSAIL), Dillon Franke(Google Project Zero), wac(Trend Micro Zero Day Initiative), Guilherme Rambo(Best Buddy Apps), Apple, Google Threat Analysis Group, Saagar Jha, Tony Iskow@@Tybbow, Google V8 Security Team, Andreas Jaegersberger & Ro Achterberg(Nosebeard Labs), rheza@@ginggilBesel(Palo Alto Networks), Edouard Bochin@@le_douds(Palo Alto Networks), Tao Yan@@Ga1ois(Palo Alto Networks), Nan Wang@@eternalsakura13, Ignacio Sanmillan@@ulexec, Jiming Wang, Jikai Ren, 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), Wang Yu(Cyberserval), Andrew James Gonzalez, Richard Hyunho Im@@richeeta, Andr.Ess, Noah Gregory (wts.dev), Thibaud Kehler, 秦若涵, 崔志伟, 崔宝江, Deval Jariwala, Dalibor Milanovic, YingQi Shi@@Mas0nShi(DBAppSecurity's WeBin lab), Duy Trần@@khanhduytran0, Shehab Khan, CertiK@@CertiK, Thomas Völkl@@vollkorntomate, SEEMOO, TU Darmstadt, Kirin@@Pwnrin(Fudan University), Bohdan Stasiuk@@bohdan_stasiuk, Sourabhkumar Mishra, @@RenwaX23, Ryan Dowd@@_rdowd

Affected Software

18 affected componentsFixes available
Apple macOS Ventura<13.7.6
13.7.6
Apple macOS Sonoma<14.7.6
14.7.6
Apple macOS Sequoia<15.5
15.5
Apple tvOS<18.5
18.5
Apple visionOS<2.5
2.5
Apple iOS<18.5
18.5
Apple iPadOS<18.5
18.5
Apple WatchOS<11.5
11.5
Apple iPadOS<17.7.7
17.7.7
Apple iPadOS<17.7.7
Apple iPadOS>=18.0<18.5
Apple iPhone OS<18.5
Apple macOS<13.7.6
Apple macOS>=14.0<14.7.6
Apple macOS>=15.0<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
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.

Peer vulnerabilities

Found alongside the following vulnerabilities.

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

CVE-2025-31233 has been classified with a high severity due to potential memory handling issues that could lead to unauthorized access.

2

How do I fix CVE-2025-31233?

To fix CVE-2025-31233, users should update to the latest versions of affected software as specified in the security advisory.

3

What products are affected by CVE-2025-31233?

CVE-2025-31233 affects several Apple products, including macOS Ventura, macOS Sonoma, macOS Sequoia, iPadOS, tvOS, visionOS, and watchOS.

4

Is there a workaround for CVE-2025-31233?

Currently, no specific workarounds are recommended for CVE-2025-31233; the best mitigation is to apply the security updates.

5

Who reported CVE-2025-31233?

CVE-2025-31233 was reported internally by Apple Security as part of their ongoing vulnerability assessments.

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