NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

CVE-2026-109413: Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process

highCVSS 4.0 8.7GHSA-2v3c-qxhr-7vpv

The Symfony Yaml component recurses without limit when it lexes deeply nested inline collections like `[[[[...]]]]`. One small YAML document can exhaust the stack and crash the PHP process or end the request with a fatal error. Any app parsing untrusted YAML is exposed. Fixed in symfony/yaml and symfony/symfony 5.4.54, 6.4.45, 7.4.18 and 8.1.6.

Published Oct 27, 2026 · Analysis Nov 1, 2026

What an attacker can do

Yaml\Parser::lexInlineStructure() calls lexInlineMapping() and lexInlineSequence() for every { and [. These calls did not enter the nesting level that the rest of the parser limits with maxNestingLevel, so the limit never applied. A document of thousands of opening brackets exhausts the stack during lexing. Depending on the PHP version and stack settings, the process crashes or the request ends in a fatal error.

The attacker needs no account. Any code path that parses untrusted YAML is reachable. The advisory names #[MapRequestPayload] as a common case: when the Yaml component is installed and the endpoint does not restrict acceptFormat, a single unauthenticated request with a YAML content type is enough. The result is denial of service (availability impact only in the CVSS 4.0 vector). Repeated requests can keep workers down.

Who is affected

symfony/yaml and symfony/symfony before 5.4.54, from 6.0 before 6.4.45, from 7.0 before 7.4.18, and from 8.0 before 8.1.6. Check what you have installed:

composer show symfony/yaml
composer show symfony/symfony

Also review endpoints that use #[MapRequestPayload] without a restricted acceptFormat, and any code calling Yaml::parse() on user input.

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 2.0.0, < 5.4.54
Fixed in
5.4.54
Check
composer show symfony/symfony

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 6.0.0, < 6.4.45
Fixed in
6.4.45
Check
composer show symfony/symfony

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 7.0.0, < 7.4.18
Fixed in
7.4.18
Check
composer show symfony/symfony

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 8.0.0, < 8.1.6
Fixed in
8.1.6
Check
composer show symfony/symfony

symfony/yaml

Ecosystem
Composer (PHP)
Affected
>= 2.0.0, < 5.4.54
Fixed in
5.4.54
Check
composer show symfony/yaml

symfony/yaml

Ecosystem
Composer (PHP)
Affected
>= 6.0.0, < 6.4.45
Fixed in
6.4.45
Check
composer show symfony/yaml

symfony/yaml

Ecosystem
Composer (PHP)
Affected
>= 7.0.0, < 7.4.18
Fixed in
7.4.18
Check
composer show symfony/yaml

symfony/yaml

Ecosystem
Composer (PHP)
Affected
>= 8.0.0, < 8.1.6
Fixed in
8.1.6
Check
composer show symfony/yaml

How to fix it

Upgrade to 5.4.54, 6.4.45, 7.4.18 or 8.1.6, depending on your branch:

composer update symfony/yaml

Use composer update symfony/symfony if you require the full package. After the fix, nested inline collections count toward maxNestingLevel and the parser throws a ParseException beyond it. The sources list no workaround. Restricting acceptFormat on exposed endpoints would reduce exposure, but the advisory does not state this.

How to tell if you were hit

Look for PHP fatal errors or segfaults (worker exits, FPM child crashes) that coincide with requests carrying a YAML content type, such as application/x-yaml or text/yaml. Unusually large request bodies made of repeated [ or { characters are the telltale payload. Check access logs for those on endpoints that deserialize request payloads. No exploit status is given in the advisory.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

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 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 the fix.

References

Credited to nicolas-grekas.

Questions

Do I need to be logged in to trigger CVE-2026-109413?

No. The advisory says a single unauthenticated request with a YAML content type is enough when #[MapRequestPayload] is used with the Yaml component installed and acceptFormat is not restricted.

Which versions fix the Symfony YAML recursion bug?

5.4.54, 6.4.45, 7.4.18 and 8.1.6 for both symfony/yaml and symfony/symfony. The patch was written for 5.4 and forward-ported to 6.4, 7.4, 8.1 and 8.2.

Does this allow code execution?

No. It is a stack exhaustion. The advisory describes a process crash or fatal error, and the CVSS 4.0 vector shows only availability impact.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Composer (PHP) vulnerabilities

All Composer (PHP) entries