Is phpcsstandards/phpcsutils 1.2 vulnerable?
Composer · 4 releases from 1.2.0 to 1.2.3 · latest phpcsstandards/phpcsutils is 1.2.3 · checked 18 Nov 2026
No known advisories in the last release
phpcsstandards/phpcsutils 1.2.3, the last 1.2 release, has no known advisories. 1 advisory affects earlier 1.2.x releases, so update to 1.2.3.
composer require phpcsstandards/phpcsutils:^1.2.3Is your project on an affected phpcsstandards/phpcsutils?
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.2.x, affecting earlier releases
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.2.x release
Affected: 1.2.0 to 1.2.2. 1.2.3 is not affected.
| Version | Known advisories |
|---|---|
| phpcsstandards/phpcsutils 1.2.3 | None |
| phpcsstandards/phpcsutils 1.2.2 | CVE-2026-65954 |
| phpcsstandards/phpcsutils 1.2.1 | CVE-2026-65954 |
| phpcsstandards/phpcsutils 1.2.0 | CVE-2026-65954 |
Which of your client projects are still on phpcsstandards/phpcsutils 1.2?
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.