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

CVE-2026-109449: Symfony Expression Language DOS Vulnerability

CVE-2026-109449 is a denial of service vulnerability in Symfony Expression Language that crashes PHP processes through deeply nested expressions. This post explains its impact, affected versions, and mitigation steps.

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-109449 Overview

CVE-2026-109449 is a denial-of-service vulnerability in the Symfony ExpressionLanguage component. The parser builds its node tree without any bound on recursion depth. Attackers can submit an expression containing tens of thousands of nested unary operators, array literals, binary operators, or property accesses to crash the PHP process while the tree is being freed. The flaw is tracked as [CWE-674: Uncontrolled Recursion].

Any application that parses untrusted expressions is exposed. The #[Assert\ExpressionSyntax] constraint forwards validated values to ExpressionLanguage::lint(), so applications that validate user-supplied expressions can be crashed with a single request.

Critical Impact

A single crafted expression crashes the PHP worker process, enabling remote, unauthenticated denial of service against any Symfony application exposing expression parsing to untrusted input.

Affected Products

  • symfony/expression-language through v5.4.53
  • symfony/expression-language v6.0.0-BETA1 through v6.4.47
  • symfony/expression-language v7.0.0-BETA1 through v7.4.20 and v8.0.0-BETA1 through v8.1.8

Discovery Timeline

  • 2026-10-15 - CVE-2026-109449 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-109449

Vulnerability Analysis

The ExpressionLanguage component converts a textual expression into an abstract syntax tree (AST) via a recursive-descent parser. Each nested unary operator, array literal, binary operator, or property access produces another node on the tree. Because the parser enforces no maximum depth, an attacker can submit an expression with tens of thousands of nested constructs. The resulting node tree exceeds the PHP stack when the engine later destroys it, terminating the process.

The advisory calls out the destruction path specifically: the crash occurs while the tree is being freed, not during parsing. This matters because applications that only lint() an expression without evaluating it are still vulnerable. The #[Assert\ExpressionSyntax] validator uses ExpressionLanguage::lint(), so form validation flows that accept expressions from end users become an exploitable entry point.

Root Cause

The root cause is uncontrolled recursion [CWE-674]. The parser methods for unary, binary, array, and property-access productions call themselves recursively with no depth counter and no configurable limit. The patched versions introduce a bounded depth check so overly nested expressions are rejected before the AST is constructed.

Attack Vector

Exploitation requires only network access to an endpoint that passes untrusted input to the Expression Language parser or linter. No authentication, user interaction, or privileges are needed. Common exposure points include form fields validated with #[Assert\ExpressionSyntax], administrative rule editors, and APIs that accept expression strings for filtering, routing, or policy evaluation. A single HTTP request is sufficient to terminate the handling PHP process.

Verified proof-of-concept code is not available in the referenced sources. See the Symfony Blog CVE-2026-109449 Analysis and the GitHub Security Advisory GHSA-7rpj-w9pf-39rr for maintainer analysis.

Detection Methods for CVE-2026-109449

Indicators of Compromise

  • PHP-FPM or PHP-CLI worker processes terminating with segmentation faults or stack overflow errors in correlation with HTTP requests to expression-handling endpoints.
  • Web server logs showing requests containing long repeating sequences of characters such as !, (, [, or . targeting form or API endpoints.
  • HTTP 502 or 504 responses from endpoints that invoke ExpressionLanguage::parse(), ExpressionLanguage::lint(), or #[Assert\ExpressionSyntax].

Detection Strategies

  • Inspect request bodies and query strings for anomalously high counts of nested operator characters directed at expression inputs.
  • Monitor PHP error logs for stack-related fatal errors and correlate with upstream request IDs.
  • Audit application code for use of symfony/expression-language and enumerate every entry point receiving user-controlled strings.

Monitoring Recommendations

  • Alert on repeated PHP worker crashes within a short time window on any host serving Symfony applications.
  • Track inventory of symfony/expression-language versions across repositories using software composition analysis.
  • Instrument expression-handling routes with request-size and character-frequency metrics to surface abuse patterns.

How to Mitigate CVE-2026-109449

Immediate Actions Required

  • Upgrade symfony/expression-language to version 5.4.54, 6.4.48, 7.4.21, or 8.1.9 or later, matching the Symfony release branch in use.
  • Identify every call site that invokes ExpressionLanguage::parse(), ExpressionLanguage::lint(), or applies #[Assert\ExpressionSyntax] to user-controlled input.
  • Place expression-handling endpoints behind authentication and rate limiting until patching is complete.

Patch Information

The fix is distributed through GitHub Pull Request #65690, GitHub Pull Request #66720, and GitHub Pull Request #66723. Full maintainer notes are published in GitHub Security Advisory GHSA-7rpj-w9pf-39rr and the Symfony Blog CVE-2026-109449 Analysis.

Workarounds

  • Reject input strings longer than an application-appropriate byte limit before passing them to the parser.
  • Filter or cap repetitive operator characters such as !, (, [, and . on expression inputs when upgrading cannot occur immediately.
  • Isolate expression parsing in a separate worker pool so a crash does not disrupt unrelated request handling.
bash
# Upgrade symfony/expression-language to a fixed release via Composer
composer require symfony/expression-language:^5.4.54
# Or, matching your branch:
# composer require symfony/expression-language:^6.4.48
# composer require symfony/expression-language:^7.4.21
# composer require symfony/expression-language:^8.1.9
composer update symfony/expression-language --with-dependencies

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.