Text::CSV_XS versions before 1.65 for Perl read before the start of an all-blank field under allow_whitespace in strip_trail_whitespace
Summary
| CVE | CVE-2026-110758 |
|---|---|
| State | PUBLISHED |
| Assigner | CPANSec |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-16 23:17:01 UTC |
| Updated | 2026-10-16 23:17:01 UTC |
| Description | Text::CSV_XS versions before 1.65 for Perl read before the start of an all-blank field under allow_whitespace in strip_trail_whitespace. Under allow_whitespace, strip_trail_whitespace removes trailing spaces and tabs from each unquoted field without stopping at the start of the field. For a field of only blanks it reads the byte before the field's heap buffer. If that byte is also a space or tab, it may be zeroed and the walk continue backwards, depending on what the allocator placed there. Leading blanks are normally skipped before a field is stored, but an all-blank field still arrives after a leading escape_char that differs from quote_char, or as a quoted field in getline when its line ends in two CRs. |
Risk And Classification
Problem Types: CWE-127 | CWE-127 CWE-127 Buffer Under-read
There are no known software configurations currently associated with this CVE in NVD or the CVE Program record.
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/cpan-authors/Text-CSV_XS/commit/efed7ee21177c59a5b69e787f8415... | 9b29abf9-4ab0-4765-b253-1875cd9b441e | github.com | |
| metacpan.org/release/HMBRAND/Text-CSV_XS-1.65/changes | 9b29abf9-4ab0-4765-b253-1875cd9b441e | metacpan.org | |
| 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
| Source | Time | Event |
|---|---|---|
| CNA | 2026-10-14T00:00:00.000Z | Fix committed to upstream repository. |
| CNA | 2026-10-15T00:00:00.000Z | Version 1.65 released with fix. |
Solutions
CNA: Upgrade to Text-CSV_XS 1.65 or later.
There are currently no legacy QID mappings associated with this CVE.