Vulnerability in phpcsstandards/phpcsutils (CVE-2026-65954)
Summary
Vulnerability in phpcsstandards/phpcsutils (CVE-2026-65954). Successful exploitation can lead to full system takeover. Exploitable via AbstractArrayDeclarationSniff. Mitigation: upgrade to 1.2.3 or later.
Original description
The description as published by the source.
Impact
PHPCSUtils versions 1.0.0-alpha1 through 1.2.2 contain an arbitrary code execution vulnerability in PHPCSUtils\AbstractSniffs\AbstractArrayDeclarationSniff::getActualArrayKey(). The vulnerable method is reached by any sniff that extends AbstractArrayDeclarationSniff and calls getActualArrayKey().
Running PHPCS over untrusted PHP code through such a sniff, for example, in a CI pipeline that lints pull requests, or on a developer machine reviewing third-party code, could lead to arbitrary command execution on the scanning host.
The vulnerability happens when the method determines the value of an array key using eval(). A maliciously crafted array key such as 'system'('id') would be executed when the code was scanned.
Known attack vectors
Known code paths that reach the vulnerable method include the following PHPCSExtra sniffs:
Universal.Arrays.DuplicateArrayKeyUniversal.Arrays.MixedArrayKeyTypes
Other packages that call AbstractArrayDeclarationSniff::getActualArrayKey() may also be vulnerable.
Patches
This issue has been fixed in PHPCSUtils 1.2.3. We recommend all users upgrade to 1.2.3 or later.
Workaround
Users who cannot upgrade immediately can disable the sniffs that reach the vulnerable method by adding `` tags to their custom ruleset (replace the placeholder standard and sniff names with the ones used in your setup):
For example, to disable the two PHPCSExtra sniffs listed under "Known attack vectors"…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65954 has been found in phpcsstandards/phpcsutils.
Attackers can target a specific entry point like AbstractArrayDeclarationSniff over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.6/10.
What to do: upgrade phpcsstandards/phpcsutils to 1.2.3 or later.
If unsure, ask your IT team or search "phpcsstandards/phpcsutils CVE-2026-65954" on the vendor's site.
CVE-2026-65954 (phpcsstandards/phpcsutils) — CWE-95 / CVSS v3 8.6
Attack vector: local / unauthenticated
Attack surface: AbstractArrayDeclarationSniff / Universal.Arrays.DuplicateArrayKey / Universal.Arrays.MixedArrayKeyTypes
Patched: 1.2.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-95) exists in phpcsstandards/phpcsutils. Attackers reach the vulnerable code path via AbstractArrayDeclarationSniff without authentication.
Check the vendor advisory for the affected versions of phpcsstandards/phpcsutils. Attack surface: AbstractArrayDeclarationSniff / Universal.Arrays.DuplicateArrayKey / Universal.Arrays.MixedArrayKeyTypes.
Severity: High (CVSS 8.6/10). Successful exploitation can lead to full system takeover.
Update to 1.2.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'phpcsstandards/phpcsutils' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'phpcsstandards/phpcsutils' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phpcsstandards/phpcsutilsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade phpcsstandards/phpcsutils to 1.2.3ステージング環境で 1.2.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web security-advisories@github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com