GHSA-26HP-CGJJ-M2J3

GHSA-26HP-CGJJ-M2J3 is a high-severity OS command injection vulnerability in fuel/core (composer), affecting versions < 1.8.0.4. It is fixed in 1.8.0.4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

fuel/core ImageMagick driver does not escape all shell arguments.

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

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

Affected versions

fuel/core (< 1.8.0.4)

Security releases

fuel/core → 1.8.0.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade fuel/core to 1.8.0.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-26HP-CGJJ-M2J3? GHSA-26HP-CGJJ-M2J3 is a high-severity OS command injection vulnerability in fuel/core (composer), affecting versions < 1.8.0.4. It is fixed in 1.8.0.4. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
  2. Which versions of fuel/core are affected by GHSA-26HP-CGJJ-M2J3? fuel/core (composer) versions < 1.8.0.4 is affected.
  3. Is there a fix for GHSA-26HP-CGJJ-M2J3? Yes. GHSA-26HP-CGJJ-M2J3 is fixed in 1.8.0.4. Upgrade to this version or later.
  4. Is GHSA-26HP-CGJJ-M2J3 exploitable, and should I be worried? Whether GHSA-26HP-CGJJ-M2J3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-26HP-CGJJ-M2J3 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-26HP-CGJJ-M2J3? Upgrade fuel/core to 1.8.0.4 or later.

Other vulnerabilities in fuel/core

Stop the waste.
Protect your environment with Kodem.