# CVE-2026-126673: Data::Dump::Streamer versions before 3.00 for Perl allow code injection via unescaped Regexp patterns in _dump_qr

> Attackers supplying Regexp patterns to Data::Dump::Streamer can run arbitrary Perl code when the dump is restored with eval or do.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`_dump_qr`)
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-126673, GHSA-h6p6-jc3j-2qf8, UBUNTU-CVE-2026-126673

## What is CVE-2026-126673?

CVE-2026-126673 is a code injection vulnerability, published on 12 Nov 2026. 

### Official description

Data::Dump::Streamer versions before 3.00 for Perl allow code injection via unescaped Regexp patterns in _dump_qr.

A Regexp's pattern is written into a qr literal without escaping "$" or "@", so "@{[ ... ]}" and "${\ ... }" in the pattern run as code when the dump is evaluated. An already escaped delimiter gets a second backslash, which leaves the delimiter bare and ends the qr literal early.

An attacker who supplies a pattern that an application compiles, dumps and later restores with eval or do can run arbitrary Perl code.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

An affected version is only exploitable if your software calls _dump_qr. Many projects that include it are not exposed.


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

No fix has been published for CVE-2026-126673 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126673 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126673 is a code injection vulnerability, published on 12 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-126673 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls _dump_qr. Many projects that include it are not exposed.

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.
   If an affected version is present, also search the code for calls to _dump_qr and report whether any exist.
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-126673/ (Markdown: https://insights.sbomify.com/CVE-2026-126673/index.md)
```

## Sources

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

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