# CVE-2026-110759: 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.

> Attackers can cause data corruption by injecting a 0xFF byte into parsed CSV fields when processing specific malformed inputs, affecting applications using Text::CSV_XS.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** AZL-109760, DEBIAN-CVE-2026-110759, GHSA-v3f5-7p3g-9fm4, UBUNTU-CVE-2026-110759

## What is CVE-2026-110759?

CVE-2026-110759 is a critical vulnerability, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1286 (Improper Validation of Syntactic Correctness of Input)

## Which versions are affected by CVE-2026-110759?


## How do I fix CVE-2026-110759?

Upgrade to a fixed version.

## Is CVE-2026-110759 being exploited?

There is no known exploitation of CVE-2026-110759 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110759 and fix it if it is affected.

What it is: CVE-2026-110759 is a critical vulnerability, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110759 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110759/ (Markdown: https://insights.sbomify.com/CVE-2026-110759/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110759
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110759
- OSV: https://osv.dev/vulnerability/CVE-2026-110759

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110759/
Summaries are generated and may contain mistakes; the official description above is the record.