Skip to content

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
mainfrom
support-agent/linear-832da718-f78e-4f8a-8db5-605d333b499b-bccd02f0-2968-4e90-838c-f287920eb476
Open

robocop-the-helper[bot] wants to merge 1 commit into
mainfrom
support-agent/linear-832da718-f78e-4f8a-8db5-605d333b499b-bccd02f0-2968-4e90-838c-f287920eb476

Conversation

@robocop-the-helper

Copy link
Copy Markdown
Contributor

Summary

Fixes CVE-2026-108082 / GHSA-r925-mgvr-h9cc in examples/laravel: a ReDoS in HeaderUtils::split(), reachable through the Cache-Control request header (affects symfony/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 (via composer update symfony/http-foundation --with-dependencies):
    • symfony/http-foundation v7.3.7 → v7.4.23
    • symfony/deprecation-contracts v3.7.1 → v3.8.1
    • symfony/polyfill-mbstring v1.38.2 → v1.43.3

Why ^7.4.21 and not an exact 7.4.19

According 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-version 2.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-foundation reports v7.4.23.
  • vendor/bin/phpunit: 2 tests / 2 assertions pass before and after, after the README's .env / key:generate setup.
  • composer validate: valid.
  • composer audit --locked: all six http-foundation advisories, including CVE-2026-108082, are gone, and no new ones appeared.
  • ReDoS reproduction against 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, and split('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 audit still reports advisories this PR doesn't address, including laravel/framework CVE-2026-114509 (critical), symfony/yaml CVE-2026-109413 (high), and medium or low issues in laravel/framework, symfony/mime, symfony/http-kernel, symfony/routing and league/flysystem. These need separate remediation.
  • symfony/http-kernel stays at 7.3.11 next to http-foundation 7.4.23. Its constraint (^7.3) allows this and the tests pass.
  • The Laravel example isn't covered by the Playwright e2e suite.

🤖 Generated with Claude Code

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>
@robocop-the-helper
robocop-the-helper Bot requested a review from a team as a code owner November 11, 2026 18:47
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.

0 participants