Text::LineFold versions through 2019.001 for Perl duplicate the output based on the number of special break characters
Summary
| CVE | CVE-2026-8594 |
|---|---|
| State | PUBLISHED |
| Assigner | CPANSec |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-30 16:17:05 UTC |
| Updated | 2026-05-30 16:17:05 UTC |
| Description | Text::LineFold versions through 2019.001 for Perl duplicate the output based on the number of special break characters. Text::LineFold splits the input string by specific line break characters (such as VT, FF and others) into segments, but applies the break function to the entire string, not just the segment. A side effect of this is that the full input can be duplicated for each segment. Besides being incorrect, this can lead to unexpected resource consumption and possible denial of service. Note that Text::LineFold is part of the Unicode-LineBreak distribution, which may have a higher version number than the module. |
Risk And Classification
Problem Types: CWE-405 | CWE-407 | CWE-405 CWE-405 Asymmetric Resource Consumption (Amplification) | CWE-407 CWE-407 Inefficient Algorithmic Complexity
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | NEZUMI | TextLineFold | affected 2019.001 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| security.metacpan.org/patches/U/Unicode-LineBreak/2019.001/CVE-2026-8594-r1.patch | 9b29abf9-4ab0-4765-b253-1875cd9b441e | security.metacpan.org | |
| metacpan.org/release/NEZUMI/Unicode-LineBreak-2019.001/source/lib/Text/Lin... | 9b29abf9-4ab0-4765-b253-1875cd9b441e | metacpan.org | |
| github.com/hatukanezumi/Unicode-LineBreak/pull/6 | 9b29abf9-4ab0-4765-b253-1875cd9b441e | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
Workarounds
CNA: Apply the patch.
There are currently no legacy QID mappings associated with this CVE.