# CVE-2026-5713: Out-of-bounds read/write during remote profiling and asyncio process introspection when connecting to malicious target

> A malicious Python process can trigger out-of-bounds reads and writes in a privileged process via remote profiling or asyncio introspection features.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Apr 2026
- **Updated:** 31 Jul 2026
- **Also known as:** BELL-CVE-2026-5713, BIT-libpython-2026-5713, BIT-python-2026-5713, BIT-python-min-2026-5713, DEBIAN-CVE-2026-5713, GHSA-2w92-jcqh-43jc, MINI-f64h-mcjw-qmwm, PSF-2026-19, UBUNTU-CVE-2026-5713

## What is CVE-2026-5713?

CVE-2026-5713 is a medium-severity memory corruption vulnerability in CPython, published on 14 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The "profiling.sampling" module (Python 3.15+) and "asyncio introspection capabilities" (3.14+, "python -m asyncio ps" and "python -m asyncio pstree") features could be used to read and write addresses in a privileged process if that process connected to a malicious or "infected" Python process via the remote debugging feature. This vulnerability requires persistently and repeatedly connecting to the process to be exploited, even after the connecting process crashes with high likelihood due to ASLR.

Weakness: CWE-125 (Out-of-bounds Read), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-5713?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libpython` | Bitnami | From 3.14.0 | 3.14.5 |
| `python` | Bitnami | From 3.14.0 | 3.14.5 |
| `python-min` | Bitnami | From 3.14.0 | 3.14.5 |

## How do I fix CVE-2026-5713?

Upgrade libpython to 3.14.5 or later.

## Is CVE-2026-5713 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5713 and fix it if it is affected.

What it is: CVE-2026-5713 is a medium-severity memory corruption vulnerability in CPython, published on 14 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5713 in the wild and no public exploit code.

Affected packages and fixed versions:
- libpython (Bitnami): affected from 3.14.0; fixed in 3.14.5
- python (Bitnami): affected from 3.14.0; fixed in 3.14.5
- python-min (Bitnami): affected from 3.14.0; fixed in 3.14.5

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

## Sources

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

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