chore(deps): [VUL-24493 et al] audit-ignore guzzle and psr7 advisories - #559
Merged
Conversation
Up to standards ✅🟢 Issues
|
pwtyler
approved these changes
Jul 31, 2026
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
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
config.audit.ignoreentries tocomposer.jsonfor CVE-2026-59883 (guzzlehttp/guzzle, advisoryPKSA-bcdd-5xc7-gwfb) and CVE-2026-59882 (guzzlehttp/psr7, advisoryPKSA-vznr-tgp9-fd7d)require-dev: behat/mink-goutte-driver ^1.2 -> fabpot/goutte v3.3.1 -> guzzlehttp/guzzle 6.5.8 -> guzzlehttp/psr7 1.9.1fabpot/goutte ^3cannot satisfyContext
VUL-24493 | VUL-25208
Both tickets are GHAS Dependabot scans flagging dev-only transitive deps with no available patch in the installed major version line. The ratified remediation route (2026-07-28) is audit-ignore since no production exposure exists.
No patched line verification (GitHub Advisory DB):
guzzlehttp/guzzle): affected range< 7.12.3; no 6.x entry. Guzzle 6.x has no patched release.guzzlehttp/psr7): affected range< 2.12.3; no 1.x entry. PSR-7 1.x has no patched release.Prior work on these tickets:
service-samwise, open): takes a migration approach, replacingfabpot/gouttewith the Symfony BrowserKit driver to remove guzzle entirely. That is a different, larger change. This PR is the simpler audit-ignore route as ratified.fix/SITE-5995-composer-auth-fix(local): added audit-ignore entries for the same guzzle dep chain using SITE-5995 as the ticket reference, but was not pushed/merged and does not cover the psr7 advisories introduced in VUL-25208.Release
No release needed. These changes are dev-only:
composer.jsonhas norequiresection (production deps are empty). All affected packages enter the lock exclusively viarequire-dev. Shipping a new plugin version would include zero behavioral change; the ignore entries are a build-tooling config only.Evidence from
composer.json:There is no
requirekey. The plugin's runtime code has no guzzle or psr7 dependency.Test plan
composer installcompletes cleanlycomposer audit --format=jsonconfirmsPKSA-bcdd-5xc7-gwfb(CVE-2026-59883) andPKSA-vznr-tgp9-fd7d(CVE-2026-59882) appear in theignored-advisoriesoutputcomposer.lock: both packages are in thepackages-devsection;requireis emptycomposer validateexits clean for simple usage (pre-existing strict warning: missingdescriptionfield, not introduced by this PR)6EA570AA8670FE4746CFA07B2D611B67C6E7BC99)Pre-existing active advisories not addressed by this PR (all dev-only, same chain, separate scope):
guzzlehttp/guzzle: PKSA-fy2t-3c5f-827y, PKSA-qxvb-2bpp-dnk6, PKSA-bbs6-q5q9-f3t4, PKSA-pwsk-hy21-4gby, PKSA-93qv-9n9h-6k6p (CVE-2026-55767), PKSA-k22t-f949-t9g6 (CVE-2026-55568)guzzlehttp/psr7: PKSA-7qs6-zvnz-h66r (CVE-2026-55766), PKSA-gm5x-j3mz-71n9 (CVE-2026-49214), PKSA-jj5t-2zs1-dcfm (CVE-2026-48998)wp-coding-standards/wpcs: PKSA-mh9b-91zm-m1gy (CVE-2026-45293) (also dev-only viapantheon-systems/pantheon-wp-coding-standards)These are all pre-existing on
mainand are either tracked in SITE-5995 or require a separate ticket.References