How severe is GHSA-26hq-7286-mg8f?

No CVSS score has been assigned to GHSA-26hq-7286-mg8f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-26hq-7286-mg8f?

GHSA-26hq-7286-mg8f affects the following packages: magento/community-edition (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-26hq-7286-mg8f?

Update magento/community-edition to 1.14.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-26hq-7286-mg8f is resolved across your whole dependency graph.

How do I detect GHSA-26hq-7286-mg8f in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-26hq-7286-mg8f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-26hq-7286-mg8f actively exploited in the wild?

No public exploit code has been indexed for GHSA-26hq-7286-mg8f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-26hq-7286-mg8f published, and has it been updated?

GHSA-26hq-7286-mg8f was published on May 15, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Magento Patch SUPEE-9652 - Remote Code Execution using mail vulnerabilityGHSA-26hq-7286-mg8f

GHSA-26hq-7286-mg8f is a security vulnerability in magento/community-edition. A fix is available for magento/community-edition — see the affected versions and patch details below.

Published

May 15, 2024

Updated

May 15, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 15, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘magento/community-edition

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Zend Framework 1 vulnerability can be remotely exploited to execute code in Magento 1. While the issue is not reproducible in Magento 2, the library code is the same so it was fixed as well.

Note: while the vulnerability is scored as critical, few systems are affected. To be affected by the vulnerability the installation has to:

use sendmail as the mail transport agent
have specific, non-default configuration settings as described here.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 1.9.0.0&&< 1.14.3.2	1.14.3.2`composer require magento/community-edition:^1.14.3.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update magento/community-edition to 1.14.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-26hq-7286-mg8f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Zend Framework 1 vulnerability can be remotely exploited to execute code in Magento 1. While the issue is not reproducible in Magento 2, the library code is the same so it was fixed as well. Note: while the vulnerability is scored as critical, few systems are affected. To be affected by the vulnerability the installation has to: - use sendmail as the mail transport agent - have specific, non-default configuration settings as described [here](https://magento.com/security/patches/supee-9652#:~:text=settings%20as%20described-,here,-.).

O3 Security · Impact-Aware SCA

Is GHSA-26hq-7286-mg8f in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works