CVE-2026-25524 affects OpenMage LTS (Magento Long Term Support) prior to version 20.17.0. The issue arises from use of PHP filesystem and image-related functions including getimagesize(), file_exists(), and is_readable() on potentially attacker-controllable paths during image validation and media handling. In PHP, these functions can trigger deserialization when given a phar:// stream wrapper path. If an attacker can upload a crafted PHAR archive disguised as an image and cause the application to invoke one of the affected functions against a phar:// path referencing that file, PHP metadata deserialization may occur, leading to arbitrary code execution in the context of the web application. The issue is patched in OpenMage LTS 20.17.0.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
phar:// paths and other unexpected stream wrappers, and tightly restricting file upload functionality. Enforce strict server-side validation of uploaded media, store uploads outside directly processed paths where feasible, and monitor for suspicious use of phar:// references in application logs or requests. These measures are compensating controls and do not replace upgrading to the fixed version.Patch, then assume compromise.
getimagesize(), file_exists(), and is_readable(), especially where phar:// stream wrapper resolution may occur during image validation or media processing. Ensure uploaded content is validated and handled in a way that prevents PHAR deserialization via stream wrappers.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.