Is phpcsstandards/phpcsutils 1.1 vulnerable?

Composer · 4 releases from 1.1.0 to 1.1.3 · latest phpcsstandards/phpcsutils is 1.2.3 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. phpcsstandards/phpcsutils 1.1.3, the last 1.1 release, is affected by 1 known security advisory (1 high), including CVE-2026-65954. Upgrade to 1.2.3 or later to fix all of them.

Upgrade with:composer require phpcsstandards/phpcsutils:^1.2.3

Is your project on an affected phpcsstandards/phpcsutils?

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 phpcsstandards/phpcsutils 1.1.3

  • HighCVE-2026-65954GHSA-r6hr-vr92-vv2829 Sept 2026

    PHPCSUtils: Remote code execution via eval() in AbstractArrayDeclarationSniff::getActualArrayKey()

    Affected
    >=1.0.0-alpha1 <1.2.3
    Fixed in
    1.2.3

Every phpcsstandards/phpcsutils 1.1.x release

Affected: 1.1.0 to 1.1.3. Latest phpcsstandards/phpcsutils: 1.2.3.

VersionKnown advisories
phpcsstandards/phpcsutils 1.1.3CVE-2026-65954
phpcsstandards/phpcsutils 1.1.2CVE-2026-65954
phpcsstandards/phpcsutils 1.1.1CVE-2026-65954
phpcsstandards/phpcsutils 1.1.0CVE-2026-65954

Which of your client projects are still on phpcsstandards/phpcsutils 1.1?

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

Other phpcsstandards/phpcsutils 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.