# CVE-2026-110753: Text::CSV_XS versions from 1.46 before 1.65 for Perl have a use-after-free of bind_columns variables when skip_empty_rows skips an empty line in getline.

> An attacker can cause a denial of service by triggering a use-after-free in Text::CSV_XS when parsing empty lines with specific options.

- **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-109748, DEBIAN-CVE-2026-110753, GHSA-gvjh-vp76-v2mp, UBUNTU-CVE-2026-110753

## What is CVE-2026-110753?

CVE-2026-110753 is a critical use after free 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 from 1.46 before 1.65 for Perl have a use-after-free of bind_columns variables when skip_empty_rows skips an empty line in getline.

With bind_columns, the parser writes each field into the caller's own scalar without taking a reference to it. When skip_empty_rows skips an empty last line, the parser frees the current field scalar without checking whether it is bound, dropping one reference from the application's variable. The "eof" mode does the same on any empty line.

The variable is then freed while the application still references it, so later code uses freed memory and can crash the process.

Weakness: CWE-911 (Improper Update of Reference Count), CWE-416 (Use After Free)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110753 is a critical use after free 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-110753 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-110753/ (Markdown: https://insights.sbomify.com/CVE-2026-110753/index.md)
```

## Sources

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

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