CVE-2025-7425: Libxslt: libxml2: heap use-after-free in libxslt caused by atype corruption in xmlattrptr

Published Jul 10, 2025
·
Updated

A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.

Other sources

Accessibility. A logic issue was addressed with improved checks.

— Apple

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

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, ABC Research s.r.o., Mickey Jin@@patch1t, 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, Dawuge(Shuffle Team), Anonymous(Trend Micro Zero Day Initiative), Willey Lin, Arsenii Kostromin (0x3c3e), Pyrophoria, Dora Orak, Csaba Fitzl@@theevilbit(Kandji), Kirin@@Pwnrin, Minghao Lin, Jiaxun Zhu, Zhongquan Li@@Guluisacat, Koh M. Nakagawa@@tsunek0h(Kandji), an anonymous researcher(Loadshine Lab), Hikerell(Loadshine Lab), @@zlluny, Wojciech Regula(SecuRing), 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

15 affected componentsFixes available
libxslt libxslt
Apple tvOS<18.6
18.6
Apple iOS<18.6
18.6
Apple iPadOS<18.6
18.6
Apple WatchOS<11.6
11.6
Apple visionOS<2.6
2.6
Apple macOS Sequoia<15.6
15.6
Microsoft cbl2 libxslt 1.1.34-9
Microsoft cbl2 libxslt 1.1.34-8
Microsoft azl3 libxslt 1.1.43-1
Microsoft azl3 libxslt 1.1.43-3
Apple Safari<18.6
18.6
Microsoft cbl2 libxslt 1.1.34-10
Microsoft azl3 libxml2 2.11.5-8
Patch available
Microsoft azl3 libxml2 2.11.5-7
Patch available

Event History

Jul 10, 2025
Data Sourced
via Red Hat·09:47 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·01:53 PM
Data Sourced
via MITRE·01:53 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeakness
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
Jul 30, 2025
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·02:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:04 AM
Affected Software
Updated
via Microsoft·09:04 AM
DescriptionSeverity
Updated
via Microsoft·09:04 AM
SeverityAffected Software
Jan 30, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected 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-7425?

CVE-2025-7425 is classified as a medium severity vulnerability due to its potential for causing memory management issues.

2

How do I fix CVE-2025-7425?

To fix CVE-2025-7425, you should upgrade to the latest version of libxslt where the memory management flaw has been addressed.

3

What systems are affected by CVE-2025-7425?

CVE-2025-7425 affects systems running vulnerable versions of the libxslt library.

4

What are the risks of not addressing CVE-2025-7425?

Failure to address CVE-2025-7425 may lead to application instability and potential data corruption due to improper handling of ID attributes.

5

Who is responsible for the CVE-2025-7425 vulnerability?

The CVE-2025-7425 vulnerability was identified in the libxslt library, which is maintained by the open-source community.

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