# CVE-2026-110755: Text::CSV_XS versions before 1.65 for Perl allow quadratic CPU use by copying the unparsed remainder per record of CR-only input in getline.

> Attackers can cause excessive CPU consumption in Text::CSV_XS by sending CSV data with CR-only line endings, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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-109751, DEBIAN-CVE-2026-110755, GHSA-chcw-qm6q-pg64, UBUNTU-CVE-2026-110755

## What is CVE-2026-110755?

CVE-2026-110755 is a high-severity denial of service 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 quadratic CPU use by copying the unparsed remainder per record of CR-only input in getline.

With eol unset, the default, getline reads with Perl's default line separator, so input with CR-only line endings arrives as one chunk. After each record the parser copies the whole unparsed remainder into a new buffer, which the next call parses and copies again, so the work grows with the square of the input size.

A reader with default options that is sent CSV with classic Mac line endings spends seconds of CPU time on a megabyte of input.

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110755 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110755 is a high-severity denial of service 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-110755 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-110755/ (Markdown: https://insights.sbomify.com/CVE-2026-110755/index.md)
```

## Sources

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

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