Is chrome-php/chrome 1.11 vulnerable?

Composer · 1 release from 1.11.0 to 1.11.0 · latest chrome-php/chrome is 1.16.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. chrome-php/chrome 1.11.0, the last 1.11 release, is affected by 1 known security advisory (1 medium), including CVE-2025-48883. Upgrade to 1.14.0 or later to fix all of them.

Upgrade with:composer require chrome-php/chrome:^1.14.0

Is your project on an affected chrome-php/chrome?

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

Advisories affecting chrome-php/chrome 1.11.0

  • MediumCVE-2025-48883GHSA-3432-fmrf-7vmh28 May 2025

    Chrome PHP is missing encoding in `CssSelector`

    Affected
    <1.14.0
    Fixed in
    1.14.0

Which of your client projects are still on chrome-php/chrome 1.11?

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

Other chrome-php/chrome 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.