Bump composer/composer to 2.9.8 (GHSA-f9f8-rm49-7jv2)#434
Merged
Conversation
composer/composer was locked at a version affected by GHSA-f9f8-rm49-7jv2 (GITHUB_TOKEN disclosure in GitHub Actions logs). Focused `composer update composer/composer` — only that package moves.
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.
Summary
Bumps
composer/composerincomposer.lockto 2.9.8, which patches GHSA-f9f8-rm49-7jv2 (high severity, published 2026-05-13) —GITHUB_TOKENdisclosure in Composer's GitHub Actions log output.composer/composeris present in this repo'scomposer.lockas a (transitive) dependency, andcomposer auditflags the locked version.How
Focused
composer update composer/composer— no--with-all-dependencies, so only thecomposer/composerentry moves. Diff is the version / reference / url / source / time lines for that one package.Why a manual PR
This repo's
vulnerability-scanworkflow is the older inline version that runswp vuln status— it scans WordPress plugins, not Composer packages, so it never detects or remediatescomposer/composer. Repos on the sharedgeneroi/github-actions/.github/workflows/vulnerability-scan.yml@v2workflow get this auto-PR'd; this brings the inline-workflow repos in line.Separately worth considering: migrating this repo to the shared
@v2vulnerability-scan workflow socomposer auditfindings are caught and auto-PR'd going forward.Test plan
composer installresolves cleanly against the updated lock.