OS Command Injection in Perl GD _make_filehandle
CVE-2026-11526 affects the Perl GD distribution in versions before 2.86. The vulnerability is in GD::Image::_make_filehandle, which uses Perl's unsafe 2-argument open() on filename arguments. In Perl, 2-arg open() can interpret specially crafted strings as shell commands or redirections rather than literal file paths. As a result, a filename beginning with a pipe (for example, "| cmd"), ending with a pipe ("cmd |"), or beginning with a redirection operator (such as "> path" or ">> path") may be executed or treated as an output redirection. _make_filehandle is the common file-opening path used by filename-accepting GD constructors, including new, newFromPng, and newFromJpeg. Applications that pass untrusted pathname input into these constructors are therefore exposed to command injection and file overwrite/truncation. In-memory *Data variants are not affected because they do not open filesystem paths.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.