How severe is GHSA-26hp-cgjj-m2j3?

No CVSS score has been assigned to GHSA-26hp-cgjj-m2j3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-26hp-cgjj-m2j3?

GHSA-26hp-cgjj-m2j3 affects the following packages: fuel/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-26hp-cgjj-m2j3?

Update fuel/core to 1.8.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-26hp-cgjj-m2j3 is resolved across your whole dependency graph.

How do I detect GHSA-26hp-cgjj-m2j3 in my Packagist dependencies?

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

How do I mitigate GHSA-26hp-cgjj-m2j3 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-26hp-cgjj-m2j3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-26hp-cgjj-m2j3 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-26hp-cgjj-m2j3 published, and has it been updated?

GHSA-26hp-cgjj-m2j3 was published on May 15, 2024 and was last updated on November 29, 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

fuel/core ImageMagick driver does not escape all shell argumentsGHSA-26hp-cgjj-m2j3

Fix: fuel/core@95c134e

GHSA-26hp-cgjj-m2j3 is a security vulnerability in fuel/core. A fix is available for fuel/core — see the affected versions and patch details below.

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘fuel/core

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

This vulnerability may cause OS commands to be executed when you pass unvalidated image filenames containing specially crafted strings to the ImageMagick driver.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`fuel/core`	all versions	1.8.0.4`composer require fuel/core:^1.8.0.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuel/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fuel/core to 1.8.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-26hp-cgjj-m2j3 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

This vulnerability may cause OS commands to be executed when you pass unvalidated image filenames containing specially crafted strings to the ImageMagick driver.

O3 Security · Impact-Aware SCA

Is GHSA-26hp-cgjj-m2j3 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works