Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process
CVE-2026-109413
Description Yaml\Parser::lexInlineStructure() recursed through lexInlineMapping() and lexInlineSequence() for every { and [ of an inline collection, without entering the nesting level that the rest of the parser bounds with maxNestingLevel. A document made of deeply nested inline collections, such as [[[[...]]]], exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error. Any code parsing untrusted YAML is affected. That includes #[MapRequestPayload] when the Yaml component is installed and the endpoint does not restrict acceptFormat: a single unauthenticated request with a YAML content type is enough. Resolution The inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by maxNestingLevel, and the parser raises a ParseException beyond it. The patches for this issue are available [here](https://github.com/symfony/symfony/commit/2a8bf9c58d862b0c76a35ce288d1ba6a27223aad) for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2). Credits We would like to thank Nicolas Grekas for reporting the issue and providing…
Assessment
- CVSS
- 8.7 (v4.0)
- Severity
- High
- EPSS
- 0.00395% chance of exploitation in the next 30 days
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 27 October 2026
- Last updated
- 27 October 2026
- Affected
- composer · symfony/symfony, symfony/yaml
- Weakness
- CWE-674
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
At the source
References
- https://github.com/symfony/symfony/security/advisories/GHSA-2v3c-qxhr-7vpv
- https://nvd.nist.gov/vuln/detail/CVE-2026-109413
- https://github.com/symfony/symfony/pull/65688
- https://github.com/symfony/symfony/commit/116287c3b5bc057e7a0420d2e52d384e14ea9417
- https://github.com/symfony/symfony/commit/2a8bf9c58d862b0c76a35ce288d1ba6a27223aad
- https://github.com/symfony/symfony/commit/8fb436fed9658a79d220e9f2b1ba8a2095559018
- https://github.com/symfony/symfony/commit/ab61e6cfd35042f16840a00f485eab2481dd4c2a
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2026-109413.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/yaml/CVE-2026-109413.yaml
- https://github.com/symfony/symfony/releases/tag/v5.4.54
- https://github.com/symfony/symfony/releases/tag/v6.4.45
- https://github.com/symfony/symfony/releases/tag/v7.4.18
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-109413