Skip to main content

CVE-2026-110759: CWE-1286 Improper Validation of Syntactic Correctness of Input

0
Medium
VulnerabilityCVE-2026-110759cvecve-2026-110759cwe-1286
Published: 10/16/2026 (10/16/2026, 22:08:23 UTC)
Source: CVE Database V5

Description

Text::CSV_XS versions before 1.65 for Perl have an issue where parsing input that ends with a separator followed by a lone carriage return (CR) results in the parser inserting a 0xFF byte into the last field. This byte is not present in the original input and can lead to malformed UTF-8 strings when UTF-8 flagging is enabled. This occurs specifically when the last field is empty and the input ends with CR instead of CRLF. The issue causes the parser to treat the end-of-file marker as data, which may affect applications processing CSV data line by line.

Affected software

GitHub Actionsmore threats →cve
Text-CSV_XS
pkg:github/Text-CSV_XS
Affected versions
>=0 <1.65

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/16/2026, 22:48:21 UTC

Technical Analysis

The vulnerability in Text::CSV_XS before version 1.65 involves improper validation of syntactic correctness of input (CWE-1286). When parsing CSV input that ends with a separator and a lone carriage return (CR), the parser incorrectly inserts a 0xFF byte into the last field, which is not part of the original input. This leads to malformed UTF-8 strings if UTF-8 flagging is enabled. The problem arises because the parser treats the end-of-file marker as the next character in this specific scenario. This behavior can affect applications reading CRLF-terminated CSV files line by line, especially when the last column is empty.

Potential Impact

Applications using vulnerable versions of Text::CSV_XS may receive unexpected 0xFF bytes in parsed fields when processing CSV inputs ending with a separator and a lone CR. This can cause malformed UTF-8 strings and potentially disrupt data processing or validation logic that expects clean input. The issue does not indicate direct code execution or privilege escalation but may lead to data integrity or parsing errors.

Mitigation Recommendations

A fix is available in Text::CSV_XS version 1.65 and later. Users should upgrade to version 1.65 or newer to resolve this issue. No other mitigations are indicated or necessary according to the available data.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
CPANSec
Date Reserved
2026-10-14T17:07:54.223Z
State
PUBLISHED

Threat ID: 6ad2a6572cdf04f656423b17

Added to database: 10/16/2026, 22:33:59 UTC

Last enriched: 10/16/2026, 22:48:21 UTC

Last updated: 10/16/2026, 22:49:06 UTC

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses