Quick answers
- Is CVE-2026-110752 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110752 being exploited in the wild.
- How severe is CVE-2026-110752?
- 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-110752?
- 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-110752 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110752?
- 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
The vulnerability is a denial-of-service via algorithmic complexity: the fragment() function pre-allocates an array with one entry per index in a row= or col= range selector before reading any data, without clamping the range to actual data size. An attacker-controlled RFC 7111 fragment parameter allows arbitrary range values, so row=1-400000000 on a small file causes ~33 bytes per index allocation (~1.3 GB for this example). The fix changes the implementation to store ranges as [from, to] pairs and test membership on-the-fly, eliminating memory allocation proportional to selector integers.
Affected products
- cpan Text::CSV_XS before 1.65
Timeline
- 2026-10-16: disclosed
- 2026-10-14: patched