dbcve.org
Libxml2Framework / library · Xmlsoft

CVE-2025-27113

HIGH · 7.5 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 2.12.10 / 2.13.6 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-476

The code follows a pointer that is null, crashing the process. An attacker who can reliably trigger it turns the crash into a denial of service. The fix is checking for null before use and handling the failure path gracefully.

General guidance for the null pointer dereference class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Libxml2Framework / library
Affected:< 2.12.10>= 2.13.0, < 2.13.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.12.10 / 2.13.6 or later
Fixed in 2.12.102.13.6
Recommended fix High confidence

Upgrade to libxml2 2.12.10 or 2.13.6 (or later)

  1. 1. Identify the current version of libxml2 installed on your system using: `xml2-config --version` or `pkg-config --modversion libxml-2.0`
  2. 2. If using a package manager (apt, yum, dnf, brew, etc.), update to the fixed version: For Debian/Ubuntu: `sudo apt update && sudo apt install libxml2`
  3. 3. For Red Hat/Fedora/CentOS: `sudo dnf update libxml2`
  4. 4. For macOS with Homebrew: `brew update && brew upgrade libxml2`
  5. 5. For source compilation: Download libxml2 2.12.10 or 2.13.6 from https://gitlab.gnome.org/GNOME/libxml2/-/releases
  6. 6. Extract the tarball and compile: `./configure && make && sudo make install`
  7. 7. Verify the fix by checking the new version: `xml2-config --version` should show 2.12.10 or 2.13.6 or higher
  8. 8. Restart any services that use libxml2 to ensure they load the updated library
Caveat Review release notes for potential API/ABI changes between your current version and 2.12.x/2.13.x; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27113 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data