---
id: "CVE-2026-110752"
kind: "vulnerability"
aliases: ["CVE-2026-110752"]
title: "Text::CSV_XS: RFC 7111 fragment selector exhausts memory and kills the process"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "perl", "text-csv-xs", "web-apps"]
not_affected_if: ["no-request-fragment", "static-input"]
published_at: "2026-10-16T23:17:00+00:00"
first_seen_at: "2026-10-23T21:57:14+00:00"
updated_at: "2026-10-25T03:24:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110752", "first_seen_at": "2026-10-23T21:57:14+00:00"}]
---

# Text::CSV_XS: RFC 7111 fragment selector exhausts memory and kills the process

Versions of Text::CSV_XS before 1.65 expand a row or column selector in a fragment into one array element per index before reading any data, so a large range such as row=1-400000000 allocates hundreds of millions of elements. An attacker who controls the fragment string can exhaust memory and crash the Perl process.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `perl -MText::CSV_XS -e 'print $Text::CSV_XS::VERSION'` and compare against `1.65`.
- Search application dependencies for `Text::CSV_XS` and find any call to `fragment` or `csv` that takes a request-supplied fragment.

## Fix

- Upgrade Text::CSV_XS to `1.65` or later.
- Until upgraded, do not pass user-supplied fragment strings to `fragment` or `csv`, or validate ranges before calling them.

## Timeline

- 2026-10-23T21:57:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110752

## From the sources

Text::CSV_XS versions before 1.65 for Perl allow memory exhaustion by allocating one entry per index of an RFC 7111 selector in fragment.

fragment expands a row= or col= selector into an array with one element per selected index before it reads any data, and it does not clamp an explicit end column in a cell= selector to the row. Only the syntax and order of the ranges are checked, so row=1-400000000 on a two-line file allocates 400 million elements.

An application that passes a request-supplied fragment to fragment or csv can be made to exhaust memory, which ends the process with an Out of memory error that eval cannot catch.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_