cve.bz

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

no score yetEPSS 0.2%

No CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
CPANSec (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126673 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126673?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126673?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126673 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126673

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126673](https://cve.bz/cve/badge/CVE-2026-126673.svg)](https://cve.bz/cve/CVE-2026-126673)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126673"><img src="https://cve.bz/cve/badge/CVE-2026-126673.svg" alt="CVE-2026-126673"></a>

Versions

From the CNA's record in the CVE List.

ProductAffected
Data-Dump-Streamerbefore 3.00

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libdata-dump-streamer-perlno fix listedDEBIAN-CVE-2026-126673
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morelibdata-dump-streamer-perlno fix listedUBUNTU-CVE-2026-126673

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON