Skip to main content
Vulnerability Database/CVE-2026-108082

CVE-2026-108082: Symfony HTTP Foundation DoS Vulnerability

CVE-2026-108082 is a denial of service vulnerability in Symfony HTTP Foundation caused by inefficient regex parsing in HeaderUtils::split(). Attackers can exploit this to consume CPU resources with crafted headers. This article covers technical details, affected versions, impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-108082 Overview

CVE-2026-108082 is a Regular Expression Denial of Service (ReDoS) vulnerability in the Symfony PHP framework's HeaderUtils::split() function. The flaw affects symfony/http-foundation across versions 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. HeaderBag invokes the vulnerable parser whenever a Request is built, specifically for the Cache-Control header. Any application processing HTTP requests is reachable with no authentication required. A single crafted request consumes nearly a second of CPU time, and headers above 18 whitespace characters cause silent directive loss.

Critical Impact

Unauthenticated attackers can trigger CPU exhaustion with a single HTTP request, or silently bypass all Cache-Control directive parsing by exceeding pcre.backtrack_limit.

Affected Products

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

Discovery Timeline

  • 2026-10-15 - CVE-2026-108082 published to the National Vulnerability Database (NVD)
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-108082

Vulnerability Analysis

The vulnerability is classified as Uncontrolled Resource Consumption through algorithmic complexity [CWE-1333]. The HeaderUtils::split() method parses structured HTTP header values using a regular expression whose token alternative also matches whitespace, followed by a (?<!\s) lookbehind assertion. When a run of whitespace precedes a separator, the regex engine can divide that whitespace among the iterations of the enclosing repetition in exponentially many ways. The engine attempts each permutation before settling, producing catastrophic backtracking.

Measured on PHP 8.5, a run of 17 spaces inside an 8 KB header consumes approximately 813 ms of CPU per request. Processing time doubles with each additional space. From 18 spaces onward, preg_match_all() aborts at the pcre.backtrack_limit, and split() returns an empty array. Every directive of the Cache-Control header is silently dropped, which can defeat cache-sensitive security logic.

Root Cause

The root cause is an ambiguous regular expression pattern inside HeaderUtils::split(). The token alternative matches whitespace characters that are also matched elsewhere in the pattern, producing exponential ambiguity when combined with the negative lookbehind. The engine must enumerate every partition of the whitespace run before confirming a match or failing.

Attack Vector

Exploitation requires only sending an HTTP request to any Symfony-based endpoint with a malicious Cache-Control header. No authentication, session, or user interaction is required. Because HeaderBag parses this header automatically during Request construction, every route in the application is reachable. An attacker can either exhaust CPU through repeated requests or weaponize the silent-drop behavior at 18+ spaces to strip security-relevant cache directives.

See the Symfony Blog CVE-2026-108082 Analysis for full technical breakdown.

Detection Methods for CVE-2026-108082

Indicators of Compromise

  • HTTP requests containing Cache-Control headers with long contiguous runs of whitespace (17+ spaces) preceding separators such as , or =.
  • Sustained PHP-FPM or worker CPU spikes correlated with inbound requests to Symfony applications.
  • Web server logs showing elevated request latency (approaching or exceeding 800 ms) for otherwise trivial routes.
  • PHP error logs reporting preg_match_all() returning due to pcre.backtrack_limit exceeded.

Detection Strategies

  • Inspect request headers at a web application firewall (WAF) or reverse proxy for Cache-Control values exceeding a reasonable length or containing consecutive whitespace sequences.
  • Correlate per-request CPU time against request header size to surface algorithmic complexity attacks.
  • Alert on repeated requests from a single source to the same endpoint when response times are abnormally high.

Monitoring Recommendations

  • Enable PHP-FPM slow request logging with a threshold below 500 ms to capture ReDoS-triggered requests.
  • Monitor backend CPU utilization and queue depth on application servers hosting Symfony workloads.
  • Track rate of 5xx and timeout responses from upstream Symfony services behind load balancers.

How to Mitigate CVE-2026-108082

Immediate Actions Required

  • Upgrade symfony/http-foundation to v5.4.54, v6.4.46, v7.4.19, or v8.1.7 depending on the installed major version.
  • Deploy a WAF rule to reject or normalize Cache-Control request headers that contain more than a few consecutive whitespace characters.
  • Enforce request body and header size limits at the edge to reduce the attack surface for algorithmic complexity attacks.

Patch Information

Fixes are available in symfony/http-foundation versions 5.4.54, 6.4.46, 7.4.19, and 8.1.7. Review the GitHub Security Advisory GHSA-r925-mgvr-h9cc, GitHub Pull Request #66048, and GitHub Pull Request #66491 for the regex replacement details.

Workarounds

  • Strip or sanitize incoming Cache-Control headers at a reverse proxy before they reach the Symfony application.
  • Lower the PHP pcre.backtrack_limit to force earlier failure, accepting that affected requests will still drop directives silently.
  • Rate-limit unauthenticated requests per source IP to limit CPU amplification until the patch is applied.
bash
# Upgrade via Composer to a patched version
composer require symfony/http-foundation:^8.1.7
# or for the 7.4.x line
composer require symfony/http-foundation:^7.4.19
# or for the 6.4.x line
composer require symfony/http-foundation:^6.4.46
# or for the 5.4.x line
composer require symfony/http-foundation:^5.4.54

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.