Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

GHSA-jrgf-vfw2-hj26

HIGHFix: OpenMage/magento-lts@26433d1

GHSA-jrgf-vfw2-hj26 is a high-severity (CVSS 8) CWE-74 vulnerability in openmage/magento-lts. O3 Security confirms whether GHSA-jrgf-vfw2-hj26 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

RCE via PHP Object injection via SOAP Requests

Also known asCVE-2020-15244
Published
Oct 30, 2020
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐘openmage/magento-lts🐘openmage/magento-lts

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

Impact

This vulnerability allows an admin user to generate soap credentials that can be used to trigger RCE via PHP Object Injection through product attributes and a product.

Patches

The latest OpenMage Versions up from 19.4.7 and 20.0.3 have this Issue solved

Credits

Credit to Luke Rodgers for reporting

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistopenmage/magento-ltsall versions19.4.8
🐘Packagistopenmage/magento-lts20.0.0&&< 20.0.420.0.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update openmage/magento-lts to 19.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jrgf-vfw2-hj26 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jrgf-vfw2-hj26 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jrgf-vfw2-hj26. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact This vulnerability allows an admin user to generate soap credentials that can be used to trigger RCE via PHP Object Injection through product attributes and a product. ### Patches The latest OpenMage Versions up from 19.4.7 and 20.0.3 have this Issue solved ### Credits Credit to Luke Rodgers for reporting
O3 Security · Impact-Aware SCA

Is GHSA-jrgf-vfw2-hj26 in your dependencies?

O3 detects GHSA-jrgf-vfw2-hj26 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.