# CVE-2026-82560: Pod::Text versions before 6.1.1 for Perl allow CPU and memory exhaustion formatting a POD document whose =over nesting drives the margin to the output width.

> An attacker can cause CPU and memory exhaustion by supplying a maliciously nested POD document to the Pod::Text Perl library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** AZL-103320, BELL-CVE-2026-82560, DEBIAN-CVE-2026-82560, ECHO-79b7-e1d4-6b1a, GHSA-qcgj-vx8w-rqfq, OESA-2026-4202, OESA-2026-4203, OESA-2026-4204, OESA-2026-4205, ROOT-OS-DEBIAN-12-CVE-2026-82560, ROOT-OS-DEBIAN-13-CVE-2026-82560, UBUNTU-CVE-2026-82560

## What is CVE-2026-82560?

CVE-2026-82560 is a high-severity denial of service vulnerability, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pod::Text versions before 6.1.1 for Perl allow CPU and memory exhaustion formatting a POD document whose =over nesting drives the margin to the output width.

Each =over adds its indent to the margin, which wrap() subtracts from the output width to get the space available for text. When that space reaches zero, the line-splitting substitution matches the empty string, and the loop consumes no input while appending the margin padding on every pass.

Formatting an attacker-supplied POD document never returns, and the output grows until memory is exhausted.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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


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

Upgrade to a fixed version.

## Is CVE-2026-82560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82560 is a high-severity denial of service vulnerability, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82560 in the wild and no public exploit code.

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

## Sources

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

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