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

> Attackers can cause excessive CPU consumption and service unavailability by sending crafted Cache-Control headers to applications using the Symfony HTTP Foundation component.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** CLSA-2026-1792529052, CLSA-2026-1792567291, CLSA-2026-1792567795, CLSA-2026-1792567918, DEBIAN-CVE-2026-108082, GHSA-r925-mgvr-h9cc, UBUNTU-CVE-2026-108082

## What is CVE-2026-108082?

CVE-2026-108082 is a high-severity denial of service vulnerability in sensiolabs symfony, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to versions 5.4.54, 6.4.46, 7.4.19, and 8.1.7, 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.

This issue affects symfony/http-foundation v4.1.0-BETA1 through v5.4.53, v6.0.0-BETA1 through v6.4.45, v7.0.0-BETA1 through v7.4.18, and v8.0.0-BETA1 through v8.1.6.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-108082?

16 open source packages ship an affected version, including symfony/http-foundation and symfony/symfony.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfony/http-foundation` | Packagist | From 4.1.0 | 5.4.54 |
| `symfony/http-foundation` | Packagist | From 4.1.0 | 5.4.54 |
| `symfony/http-foundation` | Packagist | From 6.0.1 | 6.4.46 |
| `symfony/http-foundation` | Packagist | From 6.0.1 | 6.4.46 |
| `symfony/http-foundation` | Packagist | From 7.0.0 | 7.4.19 |
| `symfony/http-foundation` | Packagist | From 7.0.0 | 7.4.19 |
| `symfony/http-foundation` | Packagist | From 8.0.0 | 8.1.7 |
| `symfony/http-foundation` | Packagist | From 8.0.0 | 8.1.7 |
| `symfony/symfony` | Packagist | From 4.1.0 | 5.4.54 |
| `symfony/symfony` | Packagist | From 4.1.0 | 5.4.54 |
| `symfony/symfony` | Packagist | From 6.0.1 | 6.4.46 |
| `symfony/symfony` | Packagist | From 6.0.1 | 6.4.46 |
| `symfony/symfony` | Packagist | From 7.0.0 | 7.4.19 |
| `symfony/symfony` | Packagist | From 7.0.0 | 7.4.19 |
| `symfony/symfony` | Packagist | From 8.0.0 | 8.1.7 |
| `symfony/symfony` | Packagist | From 8.0.0 | 8.1.7 |

## How do I fix CVE-2026-108082?

Upgrade symfony/http-foundation to a fixed version for your release line: 5.4.54, 6.4.46, 7.4.19 or 8.1.7.

## Is CVE-2026-108082 being exploited?

There is no known exploitation of CVE-2026-108082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108082 and fix it if it is affected.

What it is: CVE-2026-108082 is a high-severity denial of service vulnerability in sensiolabs symfony, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108082 in the wild and no public exploit code.

Affected packages and fixed versions:
- symfony/http-foundation (Packagist): affected from 4.1.0; fixed in 5.4.54
- symfony/http-foundation (Packagist): affected from 4.1.0; fixed in 5.4.54
- symfony/http-foundation (Packagist): affected from 6.0.1; fixed in 6.4.46
- symfony/http-foundation (Packagist): affected from 6.0.1; fixed in 6.4.46
- symfony/http-foundation (Packagist): affected from 7.0.0; fixed in 7.4.19
- symfony/http-foundation (Packagist): affected from 7.0.0; fixed in 7.4.19
- symfony/http-foundation (Packagist): affected from 8.0.0; fixed in 8.1.7
- symfony/http-foundation (Packagist): affected from 8.0.0; fixed in 8.1.7
- symfony/symfony (Packagist): affected from 4.1.0; fixed in 5.4.54
- symfony/symfony (Packagist): affected from 4.1.0; fixed in 5.4.54
- symfony/symfony (Packagist): affected from 6.0.1; fixed in 6.4.46
- symfony/symfony (Packagist): affected from 6.0.1; fixed in 6.4.46

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108082/ (Markdown: https://insights.sbomify.com/CVE-2026-108082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108082
- OSV: https://osv.dev/vulnerability/CVE-2026-108082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108082/
Summaries are generated and may contain mistakes; the official description above is the record.