PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-67434 PHPCSStandards CVE debrief

PHP_CodeSniffer contains a command injection vulnerability in the code that generates the Gitblame, Hgblame, and Svnblame report formats. This issue allows attacker-controlled shell commands to be executed when processing files with shell metacharacters in their names, potentially impacting continuous integration pipelines and developer machines reviewing third-party code. The vulnerability is fixed in versions 3.13.6 and 4.0.2. Users should verify exposure, especially in environments scanning untrusted files.

Vendor
PHPCSStandards
Product
PHP_CodeSniffer
CVSS
HIGH 7.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-06
Original CVE updated
2026-09-10
Advisory published
2026-08-06
Advisory updated
2026-09-10

Who should care

Defenders responsible for continuous integration pipelines, developer machines, and PHP_CodeSniffer deployments should assess exposure and verify remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and mitigate the vulnerability.

Why it matters

CVE-2026-67434 is a command injection vulnerability in PHP_CodeSniffer that allows attacker-controlled shell commands to be executed. Defenders should verify exposure in continuous integration pipelines and developer machines, especially where untrusted files are scanned.

  • Verify exposure in continuous integration pipelines and developer machines
  • Check and remediate vulnerable PHP_CodeSniffer versions
  • Inventory and monitor PHP_CodeSniffer usage
  • Consider compensating controls for blame report formats

Technical summary

PHP_CodeSniffer contains a command injection vulnerability in the code that generates the Gitblame, Hgblame, and Svnblame report formats. The vulnerability allows attacker-controlled shell commands to be executed when processing files with shell metacharacters in their names. This issue requires verification of affected versions and remediation from official sources. Users of the default Full report or other non-blame reports are not affected. The vulnerability impacts continuous integration pipelines and developer machines, especially where untrusted files are scanned.

Defensive priority

Defenders should prioritize verifying exposure in continuous integration pipelines and developer machines reviewing third-party code, especially where untrusted files are scanned.

Recommended defensive actions

  • Verify if continuous integration pipelines or developer machines are exposed to untrusted files scanned by PHP_CodeSniffer
  • Check if PHP_CodeSniffer versions 3.13.6 or 4.0.2 are deployed
  • Inventory PHP_CodeSniffer usage in the organization
  • Consider compensating controls for blame report formats
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability allows attacker-controlled shell commands to be executed when processing files with shell metacharacters in their names. Users of the default Full report or other non-blame reports are not affected. This issue requires verification of affected versions and remediation from official sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-67434 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-67434

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-67434 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-67434

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.