Vulnerability advisory

CVE-2026-25524

OpenMage LTS's Phar Deserialization leads to Remote Code Execution

Published Apr 20, 2026Updated Oct 28, 2026OSV record ↗

Severity

CVSS 3.xCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Repository

Affected commits	Fixed by commit
GIT github.com/openmage/magento-lts ↗
All commits before f4dd542b878613b9f40f39e9d7e862dec085defd	`f4dd542b878613b9f40f39e9d7e862dec085defd`
Also listed as affected (105) `v20.16.0` `v20.15.0` `v20.14.0` `v20.13.0` `v20.12.2` `v20.12.1` `v20.12.0` `v20.11.0` `v20.10.1` `v21.0.0-beta2` `v20.10.0` `v20.9.0` `v20.8.0` `v20.7.0` `v20.6.0` `v20.5.0` `v20.4.0` `v20.3.0` `v20.2.0` `v20.1.1` `v20.1.0` `v20.1.0-rc7` `v20.1.0-rc6` `v20.1.0-rc5` `v20.1.0-rc4` `v20.1.0-rc3` `v20.1.0-rc2` `v20.1.0-rc1` `v20.0.18` `v20.0.17` `v20.0.16` `v20.0.15` `v20.0.13` `v20.0.12` `v20.0.11` `v20.0.10` `v20.0.8` `v20.0.7` `v20.0.6` `v20.0.5` `v20.0.4` `v20.0.3` `v20.0.2` `v20.0.1` `v20.0.0` `v19.4.4` `v19.4.3` `v19.4.2` `v19.4.1` `v19.4.0` `1.9.0.1` `1.9.1.1` `1.9.1.0-lts` `1.9.0.0` `1.8.1.0` `1.7.0.2` `1.7.0.1` `1.7.0.0` `1.6.1.0` `1.6.0.0` `1.6.0.0-rc2` `1.6.0.0-rc1` `1.6.0.0-beta1` `1.6.0.0-alpha1` `1.5.1.0` `1.5.0.1` `1.5.0.0` `1.5.0.0-rc2` `1.5.0.0-rc1` `1.5.0.0-beta2` `1.5.0.0-beta1` `1.5.0.0-alpha2` `1.5.0.0-alpha1` `1.4.2.0` `1.4.1.1` `1.4.1.0` `1.4.0.1` `1.3.2.4` `1.4.0.0` `1.4.0.0-rc1` `1.4.0.0-beta1` `1.4.0.0-alpha3` `1.4.0.0-alpha2` `1.4.0.0-alpha1` `1.3.2.3` `1.3.2.2` `1.3.2.1` `1.3.2` `1.3.1.1` `1.3.1` `1.3.0` `1.2.1.2` `1.2.1` `1.2.0.3` `1.2.0.2` `1.2.0.1` `1.2.0` `1.1.8` `1.1.7` `1.1.6` `1.1.5` `1.1.4` `1.1.3` `1.1.2` `1.1.1`

Description

Magento Long Term Support (LTS) is an unofficial, community-driven project provides an alternative to the Magento Community Edition e-commerce platform with a high level of backward compatibility. Prior to version 20.17.0, PHP functions such as getimagesize(), file_exists(), and is_readable() can trigger deserialization when processing phar:// stream wrapper paths. OpenMage LTS uses these functions with potentially controllable file paths during image validation and media handling. An attacker who can upload a malicious phar file (disguised as an image) and trigger one of these functions with a phar:// path can achieve arbitrary code execution. Version 20.17.0 patches the issue.

CVE-2026-25524

Affected versions

Repository

Description

References