# CVE-2026-7111: Use after free in Text::CSV XS

> Attackers can trigger memory corruption or crashes in Perl applications using Text::CSV_XS with registered callbacks that modify the argument stack.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2026
- **Updated:** 25 Jun 2026
- **Also known as:** AZL-85922, DEBIAN-CVE-2026-7111, GHSA-29pg-8q2m-r6xm, MGASA-2026-0370, SUSE-SU-2026:1936-1, SUSE-SU-2026:21596-1, UBUNTU-CVE-2026-7111, openSUSE-SU-2026:10774-1, openSUSE-SU-2026:20708-1

## What is CVE-2026-7111?

CVE-2026-7111 is a high-severity use after free vulnerability in HMBRAND Text::CSV_XS, published on 29 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Text::CSV_XS versions before 1.62 for Perl have a use-after-free when registered callbacks extend the Perl argument stack, which may enable type confusion or memory corruption.

The Parse, print, getline, and getline_all methods invoke registered callbacks (for example after_parse, before_print, or on_error) and cache the Perl argument stack pointer across the call. If a callback extends the argument stack enough to trigger a reallocation, the return value is written through the stale pointer into the freed buffer, and the caller reads the original $self argument as the return value instead.

Calling code that expects parsed data from getline_all receives the Text::CSV_XS object in its place, leading to logic errors or crashes. Text::CSV_XS objects used without any registered callbacks are not affected.

Weakness: CWE-825 (Expired Pointer Dereference), CWE-416 (Use After Free)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-Text-CSV_XS` | openSUSE:Tumbleweed | All versions | 1.620.0-1.1 |

Products: Hmbrand Text\.

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

Upgrade to a fixed version.

## Is CVE-2026-7111 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7111 is a high-severity use after free vulnerability in HMBRAND Text::CSV_XS, published on 29 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7111 in the wild and no public exploit code.

Affected product: HMBRAND Text::CSV_XS. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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