# CVE-2025-13837: Out-of-memory when loading Plist

> A malicious plist file can cause out-of-memory errors and denial of service in applications using Python's plistlib module.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:L/SA:N`)
- **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:** 1 Dec 2025
- **Updated:** 3 Mar 2026
- **Also known as:** AZL-109692, AZL-71267, AZL-71275, BELL-CVE-2025-13837, BIT-libpython-2025-13837, BIT-python-2025-13837, BIT-python-min-2025-13837, CLSA-2026-1773136115, DEBIAN-CVE-2025-13837, ECHO-8bc4-4724-22d3, GHSA-qhx6-hpfj-8m4g, MINI-63j8-j68g-cmcw, MINI-7vjc-3rmh-vgqj, MINI-p3vp-22rg-9xjg, MINI-p93c-hq2x-pwjg, MINI-x3cp-fw88-8qq6, PSF-2025-15, UBUNTU-CVE-2025-13837

## What is CVE-2025-13837?

CVE-2025-13837 is a low-severity denial of service vulnerability in Python Python, published on 1 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libpython` | Bitnami | All versions | 3.10.20, 3.11.15, 3.12.13, 3.13.10, 3.14.1 |
| `python` | Bitnami | All versions | 3.10.20, 3.11.15, 3.12.13, 3.13.10, 3.14.1 |
| `python-min` | Bitnami | All versions | 3.10.20, 3.11.15, 3.12.13, 3.13.10, 3.14.1 |

Products: Python Python.

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

Upgrade libpython to a fixed version for your release line: 3.10.20, 3.11.15, 3.12.13 or 3.13.10.

## Is CVE-2025-13837 being exploited?

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

## Other vulnerabilities in Python Python

- [CVE-2008-5031](https://insights.sbomify.com/CVE-2008-5031/): Integer overflow in n/a (critical 10.0)
- [CVE-2014-4650](https://insights.sbomify.com/CVE-2014-4650/): Path traversal in n/a (critical 9.8)
- [CVE-2016-5636](https://insights.sbomify.com/CVE-2016-5636/): Integer overflow in n/a (critical 9.8)
- [CVE-2007-4559](https://insights.sbomify.com/CVE-2007-4559/): Path traversal in n/a (critical 9.8)
- [CVE-2017-17522](https://insights.sbomify.com/CVE-2017-17522/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13837 is a low-severity denial of service vulnerability in Python Python, published on 1 Dec 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-13837 in the wild and no public exploit code.

Affected packages and fixed versions:
- libpython (Bitnami): affected all versions; fixed in 3.10.20, 3.11.15, 3.12.13, 3.13.10, 3.14.1
- python (Bitnami): affected all versions; fixed in 3.10.20, 3.11.15, 3.12.13, 3.13.10, 3.14.1
- python-min (Bitnami): affected all versions; fixed in 3.10.20, 3.11.15, 3.12.13, 3.13.10, 3.14.1

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-13837/ (Markdown: https://insights.sbomify.com/CVE-2025-13837/index.md)
```

## Sources

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

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