CVE-2025-10911: Libxslt: use-after-free with key data stored cross-rvt

Published Sep 24, 2025
·
Updated

A use-after-free vulnerability was found in libxslt while parsing xsl nodes that may lead to the dereference of expired pointers and application crash.

Other sources

Libxslt: use-after-free with key data stored cross-rvt

Microsoft

Affected Software

7 affected components
Gnome libxslt
Microsoft azl3 libxslt 1.1.43-1
Microsoft cbl2 libxslt 1.1.34-8
Microsoft cbl2 libxslt 1.1.34-9
Microsoft azl3 libxslt 1.1.43-3
F5 F5OS-A>=1.8.0<=1.8.3, >=1.5.1<=1.5.4
F5 F5OS-C>=1.8.0<=1.8.2, >=1.6.0<=1.6.4

Event History

Sep 24, 2025
Data Sourced
via Red Hat·03:46 PM
DescriptionSeverityAffected Software
Sep 25, 2025
CVE Published
via MITRE·03:13 PM
Data Sourced
via MITRE·03:13 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Sep 29, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:01 AM
Affected Software
Updated
via Microsoft·01:01 AM
DescriptionSeverity
Apr 13, 2026
Advisory Published
via F5·04:15 PM
Data Sourced
via F5·04:15 PM
DescriptionSeverityWeaknessAffected Software
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-10911?

CVE-2025-10911 is considered a high-severity vulnerability due to its potential to cause application crashes.

2

How do I fix CVE-2025-10911?

To fix CVE-2025-10911, update to the latest version of libxslt provided by your distribution that addresses this vulnerability.

3

What impact does CVE-2025-10911 have on my application?

CVE-2025-10911 can lead to dereferencing expired pointers, resulting in crashes and potential data loss in applications using vulnerable versions of libxslt.

4

Is my software affected by CVE-2025-10911?

If you are using libxslt from GNOME, you may be affected by CVE-2025-10911, especially if you are not running an updated version.

5

How can I determine if I am vulnerable to CVE-2025-10911?

You can determine your vulnerability to CVE-2025-10911 by checking your version of libxslt against the latest security advisories from your vendor.

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