Quick answers
- Is CVE-2026-110755 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110755 being exploited in the wild.
- How severe is CVE-2026-110755?
- Informational severity, published 16 October 2026.
- Which products and versions are affected?
- CPAN Text::CSV XS before 1.65.
- Is there a fix for CVE-2026-110755?
- Yes: fixed in 1.65. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110755 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110755?
- Check whether you run CPAN Text::CSV XS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.65
Technical details
With the default eol unset, Perl's getline reads the entire file as one chunk when it contains only CR line endings. The parser then copies the full unparsed remainder into a new _AHEAD scalar after each record, which the next call parses and copies again, resulting in O(n²/(2r)) copying cost where n is input length and r is record size. The vulnerability affects Text::CSV_XS versions before 1.65 and is fixed by re-using the _AHEAD buffer in place rather than copying.
Affected products
- CPAN Text::CSV_XS before 1.65
Timeline
- 2026-10-16: disclosed
- 2026-10-14: patched: Fix committed prior to disclosure