Is fuel/core 1.8 vulnerable?

Composer · 13 releases from 1.8.0 to 1.8.2 · latest fuel/core is 1.9.0 · checked 18 Nov 2026

No known advisories in the last release

fuel/core 1.8.2, the last 1.8 release, has no known advisories. 2 advisories affect earlier 1.8.x releases, so update to 1.8.2.

Update within 1.8:composer require fuel/core:^1.8.2

Is your project on an affected fuel/core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.8.x, affecting earlier releases

  • MediumGHSA-fgrx-4637-fcf515 May 2024

    fuel/core Crypt encryption compromised.

    Affected
    <1.8.1
    Fixed in
    1.8.1
  • HighGHSA-26hp-cgjj-m2j315 May 2024

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

    Affected
    <1.8.0.4
    Fixed in
    1.8.0.4

Every fuel/core 1.8.x release

Affected: 1.8.0 to 1.8.0.4. 1.8.1 and later are not affected. Latest fuel/core: 1.9.0.

VersionKnown advisories
fuel/core 1.8.2None
fuel/core 1.8.1.6None
fuel/core 1.8.1.5None
fuel/core 1.8.1.4None
fuel/core 1.8.1.3None
fuel/core 1.8.1.2None
fuel/core 1.8.1.1None
fuel/core 1.8.1None
fuel/core 1.8.0.4GHSA-fgrx-4637-fcf5
fuel/core 1.8.0.3GHSA-fgrx-4637-fcf5, GHSA-26hp-cgjj-m2j3
fuel/core 1.8.0.2GHSA-fgrx-4637-fcf5, GHSA-26hp-cgjj-m2j3
fuel/core 1.8.0.1GHSA-fgrx-4637-fcf5, GHSA-26hp-cgjj-m2j3
fuel/core 1.8.0GHSA-fgrx-4637-fcf5, GHSA-26hp-cgjj-m2j3

Which of your client projects are still on fuel/core 1.8?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact fuel/core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other fuel/core versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.