CVE-2026-67434

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (6)

Auto-updated Aug 6, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
github Patch Available

Specially crafted filenames can lead to command injection when using *blame report format(s) · Advisory · PHPCSStandards/PHP_CodeSniffer · GitHub

https://github.com/PHPCSStandards/PHP_CodeSniffer/security/advisories/GHSA-hmqg-cxww-wqhq
github_release Patch Available

4.0.2 - 2026-08-06

Patch available: PHPCSStandards/PHP_CodeSniffer 4.0.2

https://github.com/PHPCSStandards/PHP_CodeSniffer/releases/tag/4.0.2
github_release Patch Available

3.13.6 - 2026-08-06

Patch available: PHPCSStandards/PHP_CodeSniffer 3.13.6

https://github.com/PHPCSStandards/PHP_CodeSniffer/releases/tag/3.13.6
github_pr

Reports/*blame: properly escape file name

Fix merged in PHPCSStandards/PHP_CodeSniffer PR #1473 on 2026-08-05 — awaiting tagged release

https://github.com/PHPCSStandards/PHP_CodeSniffer/pull/1473
github_commit

commit f0e1ebb0563f (PHPCSStandards/PHP_CodeSniffer)

Fix landed in PHPCSStandards/PHP_CodeSniffer commit f0e1ebb0563f — awaiting tagged release

https://github.com/PHPCSStandards/PHP_CodeSniffer/commit/f0e1ebb0563f0e5d7f190497a787bcaf8474f3fe
github_commit

commit 7a3a6bbf153a (PHPCSStandards/PHP_CodeSniffer)

Fix landed in PHPCSStandards/PHP_CodeSniffer commit 7a3a6bbf153a — awaiting tagged release

https://github.com/PHPCSStandards/PHP_CodeSniffer/commit/7a3a6bbf153a03fa3a9413afc60bded6b764e76b

Vendor Advisories for CVE-2026-67434(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
squizlabs/php_codesniffer4.0.0, 4.0.14.0.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:32 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 18:48 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 18:45 UTCEG score recompute
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 19:33 UTCEG score recompute
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 20:24 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 08:49 UTCEG score recompute
  12. 2026-08-15 09:40 UTCEG score recompute
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-13 22:52 UTCEG score recompute
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-12 23:42 UTCEG score recompute
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-12 00:32 UTCEG score recompute
  19. 2026-08-11 01:23 UTCEG score recompute
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-09 14:40 UTCEG score recompute
  22. 2026-08-09 13:47 UTCEPSS rescore
  23. 2026-08-09 03:06 UTCEG score recompute
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 03:57 UTCEG score recompute
Show 5 more
  1. 2026-08-07 16:22 UTCEG score recompute
  2. 2026-08-07 15:43 UTCEG score recompute
  3. 2026-08-06 22:37 UTCEG score recompute▲ 7.30
  4. 2026-08-06 22:37 UTCNVD updateCVSS v3 → 7.3 · CVSS v4 → 7.3
  5. 2026-08-06 22:07 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67434?
CVE-2026-67434 is a high vulnerability published on August 6, 2026. PHPCodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards. Prior to versions 3.13.6 and 4.0.2, PHPCodeSniffer contains a command injection vulnerability in the code that generates the Gitblame, Hgblame, and Svnblame report formats. As a result, running…
When was CVE-2026-67434 disclosed?
CVE-2026-67434 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67434 actively exploited?
CVE-2026-67434 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.5% of all scored CVEs.
What is the CVSS score of CVE-2026-67434?
CVE-2026-67434 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-67434?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67434, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67434

Explore →

Is Your Infrastructure Affected by CVE-2026-67434?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs