fix(security): CVE-2026-67434 — php_codesniffer OS command injection - #2370
Merged
Conversation
The Security (composer) job started failing on every branch today: Advisory ID: PKSA-rdkp-vv9z-mjkg CVE: CVE-2026-67434 Title: OS Command injection Affected versions: <3.13.6|>=4.0.0,<4.0.2 Reported at: 2026-08-05T23:53:11+00:00 The lock held 3.13.5. Nothing here caused it — the advisory was published last night — and it affects development just as much as any branch, which is why this is its own commit rather than a rider on a dependency bump. `composer.json` already allowed the fix (`^3.9`), so only the lock moves: 3.13.5 -> 3.13.6. No constraint change, no other package touched. Verified with `composer audit --locked`, which is the set CI installs from: the CVE is absent. (A plain `composer audit` still reports it here, because this checkout's vendor/ is container-owned and still holds 3.13.5 — the lock was updated with --no-install.) The audit also reports dompdf, guzzle and phpspreadsheet advisories that CI does not fail on. Those predate today and are a separate decision; this commit deliberately does not widen its scope to them.
Contributor
Quality Report — ConductionNL/openregister @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-specs | ✅ | ||||
| test-l10n | ✅ | ||||
| composer | ✅ | ✅ 173/173 | |||
| npm | ✅ | ✅ 713/713 | |||
| PHPUnit | ✅ | ||||
| Newman | ✅ | ||||
| Playwright | ✅ | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-08-06 12:11 UTC
Download the full PDF report from the workflow artifacts.
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.
The Security (composer) job started failing on every branch today:
The lock held 3.13.5. Nothing in any branch caused this — the advisory was published last night — and it affects
developmentas much as anything else, which is why it is its own PR rather than a rider on an unrelated dependency bump.Change
composer.jsonalready allowed the fix (^3.9), so only the lock moves: 3.13.5 → 3.13.6. No constraint change, no other package touched (7 lines).Verification
composer audit --locked— the set CI installs from — no longer reports the CVE.A plain
composer auditstill does here, because this checkout'svendor/is container-owned and still holds 3.13.5; the lock was updated with--no-install. CI runscomposer installfrom the lock first, so it gets 3.13.6.Out of scope, deliberately
The audit also reports dompdf, guzzle and phpspreadsheet advisories that CI does not fail on. They predate today and are a separate decision — this PR does not widen to them.