# CVE-2026-110756: Text::CSV_XS versions before 1.65 for Perl drop the end of a record and its line ending when a UTF-8 flagged field precedes invalid UTF-8 bytes in print.

> Attackers can corrupt CSV output by causing data loss and record merging when invalid UTF-8 bytes follow valid UTF-8 fields.

- **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-109742, DEBIAN-CVE-2026-110756, GHSA-fvcq-fpcj-xxcc, UBUNTU-CVE-2026-110756

## What is CVE-2026-110756?

CVE-2026-110756 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 drop the end of a record and its line ending when a UTF-8 flagged field precedes invalid UTF-8 bytes in print.

When a record contains a UTF-8 flagged field, print holds back trailing bytes that are not valid UTF-8 at each buffer flush, so that a character split across two flushes can be completed. Nothing writes the held-back bytes after the record's final flush. A record whose last field ends in such a byte loses it, any closing quote and the line ending, while print still returns true. combine is not affected.

The next record is written onto the same line, or, when the last field was quoted, the missing closing quote makes a reader take every following record as part of that field.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-110756 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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