Is j0k3r/graby 2.0 vulnerable?

Composer · 3 releases from 2.0.0 to 2.0.2 · latest j0k3r/graby is 2.5.3 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. j0k3r/graby 2.0.2, the last 2.0 release, is affected by 1 known security advisory (1 low). Upgrade to 2.5.1 or later to fix all of them.

Upgrade with:composer require j0k3r/graby:^2.5.1

Is your project on an affected j0k3r/graby?

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 j0k3r/graby 2.0.2

  • LowGHSA-3h6j-9x8m-rg3g31 Mar 2026

    Graby has stored XSS via iframe srcdoc Attribute in htmLawed Sanitization Config

    Affected
    <2.5.1
    Fixed in
    2.5.1

Every j0k3r/graby 2.0.x release

Affected: 2.0.0 to 2.0.2. Latest j0k3r/graby: 2.5.3.

VersionKnown advisories
j0k3r/graby 2.0.2GHSA-3h6j-9x8m-rg3g
j0k3r/graby 2.0.1GHSA-3h6j-9x8m-rg3g
j0k3r/graby 2.0.0GHSA-3h6j-9x8m-rg3g

Which of your client projects are still on j0k3r/graby 2.0?

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

Other j0k3r/graby 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.