cve.bz

CVE-2026-65954 phpcsstandards phpcsutils: Eval Injection

8.6 highEPSS 0.2%Fix available

High (8.6) in phpcsstandards phpcsutils. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in phpcsstandards/phpcsutils 1.2.3.

On this page
PHPCSUtils is a suite of utility functions for use with PHP_CodeSniffer. From 1.0.0-alpha1 until 1.2.3, PHPCSUtils\AbstractSniffs\AbstractArrayDeclarationSniff::getActualArrayKey() evaluates attacker-controlled array-key expressions with eval(), allowing callback-form keys in untrusted PHP code scanned by an extending sniff to execute arbitrary commands on the scanning host. Known reachable paths include Universal.Arrays.DuplicateArrayKey and Universal.Arrays.MixedArrayKeyTypes. This issue is fixed in version 1.2.3.

Severity

CVSS 3.1

8.6 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code (Eval Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • phpcsstandards/phpcsutils (Packagist): fixed in 1.2.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-65954 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-65954?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-65954?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-65954 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
PHPCSStandards PHPCSUtils>= 1.0.0-alpha1, <= 1.2.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r6hr-vr92-vv28Packagistphpcsstandards/phpcsutils>=1.0.0-alpha1 <1.2.31.2.3

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON