CVE-2025-24855
No exploitation reported by the sources we read.
- Published2025-03-14
- Fixed in8.0.461 · 1.8.0
- WeaknessCWE-416
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restored. This is related to xsltNumberFormatGetValue, xsltEvalXPathPredicate, xsltEvalXPathStringNs, and xsltComputeSortResultInternal.
Timeline
dates in UTC- 2025-03-1402:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-24855?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-24855?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | ≥ 1.9.0, < 8.0.461 | 8.0.461 | OSV |
| 1.8 | < 1.8.0 | 1.8.0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | ≥ 1.9.0, < 8.0.461 | 8.0.461 | OSV |
| 1.8 | < 1.8.0 | 1.8.0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | ≥ 1.9.0, < 8.0.461 | 8.0.461 | OSV |
| 1.8 | < 1.8.0 | 1.8.0 | OSV |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- libxsltAlmaLinux:10all versions · fixed in 1.1.39-7.el10_0and 1 other package
- libxsltAlmaLinux:9all versions · fixed in 1.1.34-9.el9_5.1and 1 other package
- libxsltAlmaLinux:8all versions · fixed in 1.1.32-6.1.el8_10and 1 other package
Vendor advisories
libxslt: Use-After-Free in libxslt numbers.c
libxslt as a component of Red Hat Enterprise Linux 6 · libxslt-devel as a component of Red Hat Enterprise Linux 6 · libxslt-python as a component of Red Hat Enterprise Linux 6 · +1 more
Red Hat Security Advisory: OpenShift Container Platform 4.19.1 bug fix and security update
Red Hat Security Advisory: OpenShift Container Platform 4.12.77 bug fix and security update
Red Hat Security Advisory: OpenShift Container Platform 4.14.52 bug fix and security update
Red Hat Security Advisory: OpenShift Container Platform 4.13.58 bug fix and security update
Red Hat Security Advisory: OpenShift Container Platform 4.16.40 bug fix and security update
14 more advisories
Fix
- Update java to 8.0.461 · 1.8.0
- Vendor fix Red Hat Product Security RHSA-2025:9278 · 650 productsFor OpenShift Container Platform 4.19 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
- Vendor fix Red Hat Product Security RHSA-2025:8303 · 1 productFor OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platfo…
- Vendor fix Red Hat Product Security RHSA-2025:7702 · 4 productsFor OpenShift Container Platform 4.14 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
- Vendor fix Red Hat Product Security RHSA-2025:4677 · 1 productFor OpenShift Container Platform 4.13 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platfor…
- Vendor fix Red Hat Product Security RHSA-2025:4731 · 4 productsFor OpenShift Container Platform 4.16 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
- Vendor fix Red Hat Product Security RHSA-2025:7496 · 17 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Advisories and patches
- gitlab.gnome.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2025-03-14
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2025-24855?
Is CVE-2025-24855 actively exploited?
What is the CVSS score for CVE-2025-24855?
Running libxslt? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.