Answer in brief
CVE-2026-67434 records a High severity (CVSS 7.3) vulnerability in PHP_CodeSniffer gitblame report command injection via crafted filename. The current sources do not mark it as known exploited. The current feed maps squizlabs/php_codesniffer (composer), squizlabs/php_codesniffer (composer), PHPCSStandards/PHP_CodeSniffer (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-67434 records a High severity (CVSS 7.3) vulnerability in PHP_CodeSniffer gitblame report command injection via crafted filename. The current sources do not mark it as known exploited. The current feed maps squizlabs/php_codesniffer (composer), squizlabs/php_codesniffer (composer), PHPCSStandards/PHP_CodeSniffer (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps squizlabs/php_codesniffer (composer), squizlabs/php_codesniffer (composer), PHPCSStandards/PHP_CodeSniffer (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| squizlabs/php_codesniffercomposer | <3.13.6 | 3.13.6 |
| squizlabs/php_codesniffercomposer | >=4.0.0,<4.0.2 | 4.0.2 |
| PHPCSStandards/PHP_CodeSniffergeneric | < 3.13.6 || >= 4.0.0, < 4.0.2 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards. Prior to versions 3.13.6 and 4.0.2, PHP_CodeSniffer contains a command injection vulnerability in the code that generates the Gitblame, Hgblame, and Svnblame report formats. As a result, running PHP_CodeSniffer over untrusted files, for example in a continuous integration pipeline that scans pull requests, or on a developer machine reviewing third party code, could result in attacker controlled shell commands being executed when the Gitblame, Hgblame, or Svnblame report processes a file whose name contains shell metacharacters. Users using the default Full report, or any of the other non-blame reports, are not affected. Users on a runtime platform which does not allow filenames to contain shell metacharacters, such as " and ;, are not affected. This issue is fixed in versions 3.13.6 and 4.0.2.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps squizlabs/php_codesniffer (composer), squizlabs/php_codesniffer (composer), PHPCSStandards/PHP_CodeSniffer (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| squizlabs/php_codesniffercomposer | <3.13.6 | 3.13.6 |
| squizlabs/php_codesniffercomposer | >=4.0.0,<4.0.2 | 4.0.2 |
| PHPCSStandards/PHP_CodeSniffergeneric | < 3.13.6 || >= 4.0.0, < 4.0.2 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards. Prior to versions 3.13.6 and 4.0.2, PHP_CodeSniffer contains a command injection vulnerability in the code that generates the Gitblame, Hgblame, and Svnblame report formats. As a result, running PHP_CodeSniffer over untrusted files, for example in a continuous integration pipeline that scans pull requests, or on a developer machine reviewing third party code, could result in attacker controlled shell commands being executed when the Gitblame, Hgblame, or Svnblame report processes a file whose name contains shell metacharacters. Users using the default Full report, or any of the other non-blame reports, are not affected. Users on a runtime platform which does not allow filenames to contain shell metacharacters, such as " and ;, are not affected. This issue is fixed in versions 3.13.6 and 4.0.2.
Quoted source text, attributed separately from HOL analysis.