Skip to content

chore(deps): bump phpcsutils to 1.2.3 — CVE-2026-65954 (unblocks Security (composer) on every open PR) - #800

Open
rubenvdlinde wants to merge 2 commits into
developmentfrom
chore/bump-phpcsutils-cve-2026-65954
Open

chore(deps): bump phpcsutils to 1.2.3 — CVE-2026-65954 (unblocks Security (composer) on every open PR)#800
rubenvdlinde wants to merge 2 commits into
developmentfrom
chore/bump-phpcsutils-cve-2026-65954

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

See commit message. Lockfile-only dev-dependency bump; composer audit --locked goes from 1 advisory to clean. ⚠️ Could not install locally (vendor/ not writable in this checkout), so the PHP Quality (phpcs) cell on this PR is the real exercise of the bump — do not merge on the audit result alone.

… execution

`quality / Security (composer)` is failing on every open procest PR. The cause
is pre-existing and not introduced by any of them:

  Package: phpcsstandards/phpcsutils
  CVE: CVE-2026-65954 — Arbitrary code execution
  Affected: >=1.0.0-alpha1,<1.2.3   (locked at 1.2.2)
  Reported: 2026-07-27

Lockfile-only bump: phpcsutils 1.2.2 → 1.2.3, pulling phpcsextra v1.2.0 → v1.2.1
as its dependency. No composer.json constraint changes — both are already
satisfied by the existing `^1.4` / `^3.9` ranges, so this is a lock refresh,
not a constraint widening. Dev dependencies only; nothing shipped to users
changes.

`composer audit --locked` against the new lock: "No security vulnerability
advisories found." Before the bump it reported the advisory above.

`squizlabs/php_codesniffer` is already at 3.13.6, which is the fixed version
for CVE-2026-67434 ("<3.13.6"), so it needed no change — worth stating because
a local `composer audit` reading a stale vendor/ reports it as still affected.

⚠️ Verification limits, stated plainly: I could not install the new versions
locally — `vendor/` in this checkout is not writable by me, so
`composer install` failed on `vendor/bin/phpcbf`. The phpcs run I did locally
therefore exercised the OLD versions and proves nothing about the new ones. CI
installs from the lock and runs phpcs/phpcbf against it, so the `PHP Quality
(phpcs)` cell on this PR is the real exercise of this bump. If that cell is
green, the bump is verified; do not merge on the audit result alone.
The PHP 8.4 PHPUnit cell failed with:

  fatal: unable to access 'https://github.com/nextcloud/server/':
  server certificate verification failed. CAfile: none CRLfile: none
  The process '/usr/bin/git' failed with exit code 128

The 8.3 cell on the same run passed. A matrix cell that differs from its
neighbour by PHP version alone and dies while CLONING the server repo is a
runner-side network fault, not a version rule and not this lockfile bump.
`gh run rerun` refused the run, so this empty commit is the re-trigger.

No file changes.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 4e20f5e

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
check-vue3-compile
test-l10n
composer ✅ 100/100
npm ✅ 552/552
PHPUnit
Newman ⏭️
Playwright
Hydra gates

Quality workflow — 2026-08-11 19:36 UTC

Download the full PDF report from the workflow artifacts.

@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ a825811

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
check-vue3-compile
test-l10n
composer ✅ 100/100
npm ✅ 552/552
PHPUnit
Newman ⏭️
Playwright
Hydra gates

Quality workflow — 2026-08-11 19:54 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant