# CVE-2026-110757: Text::CSV_XS versions before 1.65 for Perl allow record splitting by writing strings used as numbers without quotes in combine.

> Attackers can inject newlines into numeric fields to split CSV records, corrupting data integrity in 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-109754, DEBIAN-CVE-2026-110757, GHSA-9gc4-xhw7-655h, UBUNTU-CVE-2026-110757

## What is CVE-2026-110757?

CVE-2026-110757 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 allow record splitting by writing strings used as numbers without quotes in combine.

combine and print do not check whether a field needs quotes when its value has Perl's integer or numeric flag set. Perl sets these flags on a string used in a numeric operation when it parses as a number, which allows leading and trailing whitespace. With binary set, as csv does by default, "12\n" passes a check such as $qty > 0 and is then written unquoted with its newline.

A value validated as a number can end the record early and turn the fields after it into a separate row.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110757 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110757 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-110757 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-110757/ (Markdown: https://insights.sbomify.com/CVE-2026-110757/index.md)
```

## Sources

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

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