CPU and memory exhaustion via zero-width wrapping loop
Published Sep 19, 2026 · Updated Sep 19, 2026
Resource exhaustion in Pod::Text before 6.1.1 allows attackers to hang a formatting process with a crafted POD document. Nested =over directives can make the accumulated margin equal the output width, so wrap() repeatedly matches zero characters while appending padding without consuming input. Exploitation requires an application to format attacker-supplied POD; the process consumes CPU indefinitely and grows its output until memory is exhausted.
Summary
What happened
Resource exhaustion in Pod::Text before 6.1.1 allows attackers to hang a formatting process with a crafted POD document. Nested =over directives can make the accumulated margin equal the output width, so wrap() repeatedly matches zero characters while appending padding without consuming input. Exploitation requires an application to format attacker-supplied POD; the process consumes CPU indefinitely and grows its output until memory is exhausted.
The record
- CVE
- CVE-2026-82560
- Published
- Sep 19, 2026
- Updated
- Sep 19, 2026
- Vendor
- Russ Allbery
- Product
- Podlators
- Classifications
- CWE-835, T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 19, 2026CVE publishedPublication date reported by the CVE source.
- Sep 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started