CVE-2025-27113

What it actually does

NULL pointer dereference in xmlPatMatch within pattern.c leads to memory corruption and potential application crash or undefined behavior when processing crafted pattern inputs.

Why it matters to the business

Widespread denial-of-service risk across applications and libraries depending on libxml2, including 98 downstream dependents such as TensorFlow deployments, resulting in service outages and operational disruption.

How an attack unfolds

An attacker identifies an application or service using a vulnerable libxml2 version and supplies specially crafted XML pattern data that reaches xmlPatMatch, triggering the NULL dereference to crash the process or potentially escalate into further memory corruption.

How to fix it

Upgrade libxml2 to version 2.12.10 or later, or 2.13.6 or later. For TensorFlow (Bitnami) update to 2.1.4. For gnome/libxml2 (GIT) apply commit 02d577715e1951cf114ca4e9adaf5605156c4f4c. Rebuild and redeploy dependent applications after upgrade.

How to confirm the fix worked

Verify installed libxml2 version against fixed releases, run regression tests with pattern-matching workloads, and monitor for absence of NULL dereference crashes under expected input conditions.

Typical attack path

1. Locate target application or service relying on affected libxml2
2. Craft malicious input targeting xmlPatMatch in pattern.c
3. Deliver input via XML parsing or pattern matching functionality
4. Trigger NULL dereference leading to crash or memory corruption

How to detect it

Monitor application logs and crash dumps for segmentation faults or NULL pointer errors originating from libxml2 pattern matching functions; review XML input sources feeding into pattern.c processing.

What your security team should do

• Prioritize upgrade of libxml2 in all affected products and dependents within standard patching cycles
• Inventory applications using libxml2 to assess exposure breadth
• Test upgrades in staging environments before production rollout