Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE
CVE-2026-67434 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 comman… https://www.cve.org/CVERecord?id=CVE-2026-67434
Post summary
The post notes that PHP_CodeSniffer had a vulnerability in pre‑3.13.6 and pre‑4.0.2 releases, but provides little technical detail and no exploit or patch information.
🚨*CVE* CVE-2026-67434 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 comman… https://www.cve.org/CVERecord?id=CVE-2026-67434 ----- Traducción: CVE-2026-67434 PHP… http://infoflow.cloud`
Post summary
The post simply points to CVE‑2026‑67434 and notes affected versions of PHP_CodeSniffer, without providing details on exploitation, patches, or technical specifics.