Repository navigation
Upgrade symfony/http-foundation to 7.4.23 in the Laravel example (CVE-2026-108082) - #119
Open
robocop-the-helper[bot] wants to merge 1 commit into
Conversation
Fixes CVE-2026-108082 (GHSA-r925-mgvr-h9cc): ReDoS in HeaderUtils::split() reachable through the Cache-Control request header, affecting symfony/http-foundation >=7.0.0 <7.4.19. Replace the exact 7.3.7 pin with ^7.4.21. The advisory names 7.4.21 as the safest 7.4 target, because 7.4.19-7.4.20 regressed splitting on whitespace separators. Updated with `composer update symfony/http-foundation --with-dependencies`, which also bumps symfony/deprecation-contracts (3.7.1 -> 3.8.1) and symfony/polyfill-mbstring (1.38.2 -> 1.43.3). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Fixes CVE-2026-108082 / GHSA-r925-mgvr-h9cc in
examples/laravel: a ReDoS inHeaderUtils::split(), reachable through theCache-Controlrequest header (affectssymfony/http-foundation>=7.0.0 <7.4.19). Resolves SECSLOP-10 and Dependabot alert #1867.composer.json:"symfony/http-foundation": "7.3.7"→"^7.4.21"composer.lock(viacomposer update symfony/http-foundation --with-dependencies):symfony/http-foundationv7.3.7 → v7.4.23symfony/deprecation-contractsv3.7.1 → v3.8.1symfony/polyfill-mbstringv1.38.2 → v1.43.3Why
^7.4.21and not an exact7.4.19According to the advisory, the first fix broke splitting on whitespace separators in 7.4.19–7.4.20. 7.4.21 fixes that, and the advisory calls it the safest 7.4 target. The caret range also allows later patch releases, which the old exact pin blocked.
The lock was written with the repo's
composer.phar(2.8.8), which also changed some metadata (plugin-api-version2.3.0 → 2.6.0,[]→{}). This doesn't change which packages are installed.Verification
composer install(from the lockfile) succeeds before and after the change.composer show symfony/http-foundationreports v7.4.23.vendor/bin/phpunit: 2 tests / 2 assertions pass before and after, after the README's.env/key:generatesetup.composer validate: valid.composer audit --locked: all six http-foundation advisories, including CVE-2026-108082, are gone, and no new ones appeared.HeaderBag: on 7.3.7, a Cache-Control value with 18 spaces before a separator drops every directive. On 7.4.23 the directives parse correctly, andsplit('foo bar', ' ')still returns both parts.biome ci .and the Biome version check pass.Package age check: Composer can't enforce a minimum release age and the repo sets none for it, so I checked Packagist publication dates instead: http-foundation v7.4.23 is from 2026-11-04, polyfill-mbstring v1.43.3 from 2026-10-28 and deprecation-contracts v3.8.1 from 2026-09-16.
Remaining risks / follow-ups
composer auditstill reports advisories this PR doesn't address, includinglaravel/frameworkCVE-2026-114509 (critical),symfony/yamlCVE-2026-109413 (high), and medium or low issues inlaravel/framework,symfony/mime,symfony/http-kernel,symfony/routingandleague/flysystem. These need separate remediation.symfony/http-kernelstays at 7.3.11 next to http-foundation 7.4.23. Its constraint (^7.3) allows this and the tests pass.🤖 Generated with Claude Code