Advisory

GHSA-r925-mgvr-h9cc

Also known as: CVE-2026-108082

Summary

Symfony: ReDoS in HeaderUtils::split() Reachable Through the Cache-Control Request Header

Details

Description

HeaderUtils::split() parsed header values with a pattern whose token alternative also matched whitespace, followed by a (?<!\s) lookbehind. A run of whitespace placed before a separator could be divided among the iterations of the enclosing repetition in exponentially many ways, and the engine tried all of them before settling. HeaderBag calls it for the Cache-Control header whenever a Request is built, so any application handling HTTP requests is reachable, with no authentication.

A single request carrying such a header costs close to a second of CPU (813 ms for a run of 17 spaces in an 8 KB header on PHP 8.5, doubling with each extra space). From 18 spaces on, preg_match_all() gives up at pcre.backtrack_limit and split() returns an empty array, so every directive of the header is silently dropped.

Resolution

The pattern now consumes whitespace only when more of the value follows it, so a value can no longer end on whitespace, nothing has to be given back, and every quantifier is possessive. The first release of this fix broke splitting on a whitespace separator: HeaderUtils::split('foo bar', ' ') returned a single value in 6.4.46 to 6.4.47, 7.4.19 to 7.4.20 and 8.1.7 to 8.1.8. Whitespace characters used as separators are now left out of the whitespace branch, which 6.4.48, 7.4.21 and 8.1.9 contain.

The patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).

Credits

Symfony would like to thank r3verii for reporting the issue and Nicolas Grekas for providing the fix.

Symfony would also like to thank Bruno Dias from Checkmarx for his help getting a CVE assigned.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-10-27 19:01 UTC
Modified
2026-10-27 19:15 UTC

Affected packages and fixes

symfony/http-foundation

Packagist · All systems

Affected

  • introduced 6.0.1, fixed 6.4.46 (ecosystem)

Fixed versions

6.4.46

Fix

The export has no generic command for this ecosystem.

symfony/http-foundation

Packagist · All systems

Affected

  • introduced 7.0.0, fixed 7.4.19 (ecosystem)

Fixed versions

7.4.19

Fix

The export has no generic command for this ecosystem.

symfony/http-foundation

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.1.7 (ecosystem)

Fixed versions

8.1.7

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 6.0.1, fixed 6.4.46 (ecosystem)

Fixed versions

6.4.46

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 7.0.0, fixed 7.4.19 (ecosystem)

Fixed versions

7.4.19

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.1.7 (ecosystem)

Fixed versions

8.1.7

Fix

The export has no generic command for this ecosystem.

symfony/http-foundation

Packagist · All systems

Affected

  • introduced 4.1.0, fixed 5.4.54 (ecosystem)

Fixed versions

5.4.54

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 4.1.0, fixed 5.4.54 (ecosystem)

Fixed versions

5.4.54

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences