chore(security): bump squizlabs/php_codesniffer to 4.0.4 (CVE-2026-67434) - #8
Merged
Merged
Conversation
) New HIGH advisory: CVE-2026-67434 — OS Command injection — GHSA-hmqg-cxww-wqhq Affects <3.13.6 and >=4.0.0,<4.0.2. This repo was locked at 4.0.1. composer.json already allows ^4.0, so only the lock moves. Produced with `composer update squizlabs/php_codesniffer --no-install` so vendor/ is untouched — file count identical before and after. ⚠ This repo has NO composer audit gate in CI, so nothing here would ever have reported this. Found only because phlix-server's custom audit script went red on the same advisory. The missing gate is filed as its own step.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
🟢 Coverage ∅ diff coverage · +0.00% coverage variation
Metric Results Coverage variation ✅ +0.00% coverage variation (-1.00%) Diff coverage ✅ ∅ diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (d24e484) 9 9 100.00% Head commit (e159c2c) 9 (+0) 9 (+0) 100.00% (+0.00%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#8) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CVE-2026-67434 —
squizlabs/php_codesnifferOS command injection (HIGH)Locked at 4.0.1; the advisory affects
<3.13.6and>=4.0.0,<4.0.2, sothe 4.x line is in range too. Bumped to 4.0.4.
composer.jsonalready allows^4.0, so onlycomposer.lockmoves.GHSA-hmqg-cxww-wqhq
🔴 Nothing in this repo would ever have reported it
This repo has no composer audit step in CI at all. It was found only because
phlix-server uses a custom
scripts/security-audit-check.phpthat auditsevery dependency, and went red on the same advisory.
Estate survey run at the same time:
composer audit --no-dev— blind to require-devThe missing gate is filed as its own step rather than bolted on inside a security
bump — it needs a policy decision (audit everything and fix promptly, vs. audit
dev separately and report non-blocking) and a demonstration that the new gate can
actually go red.
vendor/untouched, verifiedProduced with
composer update squizlabs/php_codesniffer --no-install, so theworking tree's
vendor/never changed — file count identical before and after,and
git status --porcelainshowedM composer.lockalone. CI does its own cleaninstall and will resolve 4.0.4 from the lock.