# CVE-2025-11468: Folding email comments of unfoldable characters doesn't preserve parenthesis

> Attackers can inject headers into emails by exploiting improper folding of comments with unfoldable characters in Python's email library.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Jan 2026
- **Updated:** 3 Mar 2026
- **Also known as:** AZL-75035, AZL-75047, BELL-CVE-2025-11468, BIT-libpython-2025-11468, BIT-python-2025-11468, BIT-python-min-2025-11468, DEBIAN-CVE-2025-11468, ECHO-246d-6bd6-6778, GHSA-39h2-3mq3-959g, MINI-6r2c-f8j3-rg9g, MINI-9cj5-c382-h69r, MINI-h6p2-f839-72qv, MINI-m9p9-m699-3w25, MINI-rv2h-rvvv-4fh9, PSF-2026-1, UBUNTU-CVE-2025-11468, openSUSE-SU-2026:10117-1

## What is CVE-2025-11468?

CVE-2025-11468 is a medium-severity vulnerability in CPython, published on 20 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libpython` | Bitnami | All versions | 3.10.20, 3.11.15, 3.12.13, 3.13.12, 3.14.3 |
| `python` | Bitnami | All versions | 3.10.20, 3.11.15, 3.12.13, 3.13.12, 3.14.3 |
| `python-min` | Bitnami | All versions | 3.10.20, 3.11.15, 3.12.13, 3.13.12, 3.14.3 |
| `python314` | openSUSE:Tumbleweed | All versions | 3.14.2-2.1 |

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

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

## Is CVE-2025-11468 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11468 is a medium-severity vulnerability in CPython, published on 20 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-11468 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.12, 3.14.3
- python (Bitnami): affected all versions; fixed in 3.10.20, 3.11.15, 3.12.13, 3.13.12, 3.14.3
- python-min (Bitnami): affected all versions; fixed in 3.10.20, 3.11.15, 3.12.13, 3.13.12, 3.14.3

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

## Sources

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

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