# CVE-2025-27113: Null dereference in libxml2

> A NULL pointer dereference in libxml2 allows attackers to cause a denial of service via crafted XML patterns.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2025
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2025-27113, AZL-56964, AZL-57058, BELL-CVE-2025-27113, BIT-java-2025-27113, BIT-java-min-2025-27113, BIT-jre-2025-27113, CLSA-2025-1741215702, CLSA-2025-1741286016, CLSA-2025-1741291888, CLSA-2025-1741628775, CLSA-2025-1741629091, CLSA-2025-1741629104, CLSA-2025-1741629749, CLSA-2025-1741636522, CLSA-2025-1764958229, DEBIAN-CVE-2025-27113, ECHO-349d-8c18-8761, GHSA-m9m6-wcr9-hh75, JLSEC-2025-88, MINI-628c-j9fq-rgcj, MINI-8fjv-5vwc-27ch, ROOT-OS-ALPINE-315-CVE-2025-27113, UBUNTU-CVE-2025-27113

## What is CVE-2025-27113?

CVE-2025-27113 is a low-severity vulnerability in Xmlsoft Libxml2, published on 18 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-27113?

3 open source packages ship an affected version, including java, java-min and jre. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java` | Bitnami | All versions | 1.8.0, 8.0.461 |
| `java-min` | Bitnami | All versions | 1.8.0, 8.0.461 |
| `jre` | Bitnami | All versions | 1.8.0, 8.0.461 |

Products: Xmlsoft Libxml2.

## How do I fix CVE-2025-27113?

Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.461.

## Is CVE-2025-27113 being exploited?

There is no known exploitation of CVE-2025-27113 in the wild and no public exploit code.

## Other vulnerabilities in Xmlsoft Libxml2

- [CVE-2017-16931](https://insights.sbomify.com/CVE-2017-16931/): XML external entity in n/a (critical 9.8)
- [CVE-2017-8872](https://insights.sbomify.com/CVE-2017-8872/): Information disclosure in n/a (critical 9.1)
- [CVE-2022-49043](https://insights.sbomify.com/CVE-2022-49043/): Use after free in libxml2 (high 8.1)
- [CVE-2026-86140](https://insights.sbomify.com/CVE-2026-86140/): Memory corruption in libxml2 (high 8.0)
- [CVE-2024-34459](https://insights.sbomify.com/CVE-2024-34459/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27113 and fix it if it is affected.

What it is: CVE-2025-27113 is a low-severity vulnerability in Xmlsoft Libxml2, published on 18 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27113 in the wild and no public exploit code.

Affected packages and fixed versions:
- java (Bitnami): affected all versions; fixed in 1.8.0, 8.0.461
- java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.461
- jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.461

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27113/ (Markdown: https://insights.sbomify.com/CVE-2025-27113/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27113
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27113
- OSV: https://osv.dev/vulnerability/CVE-2025-27113

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27113/
Summaries are generated and may contain mistakes; the official description above is the record.