Live › vulnerability › CVE-2026-110759
Go to dashboardText::CSV_XS before 1.65 for Perl inserts a stray 0xFF byte into the last field when input ends with a separator and a lone CR. The application receives a byte that was not in its input, and UTF-8 flagged input yields malformed UTF-8.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Check the installed Text::CSV_XS version and confirm it is below 1.65.
Upgrade Text::CSV_XS to 1.65 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Text::CSV_XS versions before 1.65 for Perl return a 0xFF byte that is not in the input for an empty last field followed by a lone CR in parse.
When the input to parse ends in a separator and a lone CR, the parser treats the end of the input as the next character and stores the end-of-file marker in the field as the byte 0xFF. With binary set, parse("a,\r") returns the fields "a" and "\xFF". On UTF-8 flagged input the last field is a UTF-8 flagged string holding that lone byte, which is malformed UTF-8. The same input with a non-empty last field is rejected as an error.
A CRLF file read line by line and chomped ends this way when its last column is empty, so the application receives a byte that is not in its input.
This page as .md · .json · in your agent: get_signal("CVE-2026-110759")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.