How severe is GHSA-hmqg-cxww-wqhq?

No CVSS score has been assigned to GHSA-hmqg-cxww-wqhq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hmqg-cxww-wqhq?

GHSA-hmqg-cxww-wqhq affects the following packages: squizlabs/php_codesniffer (Packagist), squizlabs/php_codesniffer (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-hmqg-cxww-wqhq?

Update squizlabs/php_codesniffer to 3.13.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hmqg-cxww-wqhq is resolved across your whole dependency graph.

How do I detect GHSA-hmqg-cxww-wqhq in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for squizlabs/php_codesniffer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hmqg-cxww-wqhq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hmqg-cxww-wqhq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hmqg-cxww-wqhq can be triaged on real exposure rather than presence alone.

Is GHSA-hmqg-cxww-wqhq actively exploited in the wild?

No public exploit code has been indexed for GHSA-hmqg-cxww-wqhq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hmqg-cxww-wqhq?

GHSA-hmqg-cxww-wqhq has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hmqg-cxww-wqhq?

GHSA-hmqg-cxww-wqhq is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-hmqg-cxww-wqhq published, and has it been updated?

GHSA-hmqg-cxww-wqhq was published on August 6, 2026 and was last updated on August 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-hmqg-cxww-wqhq — squizlabs/php_codesniffer

Fix: PHPCSStandards/PHP_CodeSniffer#1473

GHSA-hmqg-cxww-wqhq is a OS Command Injection vulnerability in squizlabs/php_codesniffer. A fix is available for squizlabs/php_codesniffer — see the affected versions and patch details below.

PHP_CodeSniffer gitblame report command injection via crafted filename

Also known asCVE-2026-67434

Published

Aug 6, 2026

Updated

Aug 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hmqg-cxww-wqhq.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐘squizlabs/php_codesniffer🐘squizlabs/php_codesniffer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

PHP_CodeSniffer versions before v3.13.6 and v4.0.2 contain a command injection vulnerability in the code creating the Gitblame, Hgblame and Svnblame report(s).

As a result, running PHP_CodeSniffer over untrusted files, for example, in a CI 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(s) would process 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.

Patched versions

The issue has been fixed in PHP_CodeSniffer v3.13.6 and v4.0.2. We recommend all users upgrade to these versions at their earliest convenience.

Workaround

Users of PHP_CodeSniffer who cannot upgrade immediately should ensure they do not use the Gitblame, Hgblame or the Svnblame reports when scanning untrusted code.

This is especially relevant for CI jobs, pre-commit or review tooling, automated review services, and any service that scans untrusted repositories or uploaded source trees.

Credits

Many thanks to both @Faze-up and @edorian for responsibly disclosing this vulnerability.

How can I report a security bug?

Please report security vulnerabilities privately via the "Security and quality" tab on the PHP_CodeSniffer repository.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`squizlabs/php_codesniffer`	all versions	3.13.6`composer require squizlabs/php_codesniffer:^3.13.6`
🐘Packagist	`squizlabs/php_codesniffer`	≥ 4.0.0&&< 4.0.2	4.0.2`composer require squizlabs/php_codesniffer:^4.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for squizlabs/php_codesniffer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update squizlabs/php_codesniffer to 3.13.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hmqg-cxww-wqhq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hmqg-cxww-wqhq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hmqg-cxww-wqhq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact PHP_CodeSniffer versions before v3.13.6 and v4.0.2 contain a command injection vulnerability in the code creating the `Gitblame`, `Hgblame` and `Svnblame` report(s). As a result, running PHP_CodeSniffer over untrusted files, for example, in a CI 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(s) would process a file whose name contains shell metacharacters. * Users using the default `Full` report, or any of the other non-*b

O3 Security · Impact-Aware SCA

Is GHSA-hmqg-cxww-wqhq in your dependencies?

O3 Security finds GHSA-hmqg-cxww-wqhq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works