Patch Forecast
Amber warning
Patch this week.

CVE-2026-109413

In Symfony YAML prior to versions 5.4.54, 6.4.45, 7.4.18…

Risk score
66/100
CVSS
8.7 v4.0
Exploit chance (30 days)
0.5%
Published
15 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is
In Symfony YAML prior to versions 5.4.54, 6.4.45, 7.4.18, and 8.1.6, 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 de…
Affected
See advisory
Fix
Upgrade the product to 5.4.54, 6.4.45, 7.4.18 or 8.1.6 (whichever matches your release line), or later.
Exploitation
No known exploitation

Why it is Amber

  • CVSS 8.7 high
  • Remotely exploitable without logging in

References

Original description

In Symfony YAML prior to versions 5.4.54, 6.4.45, 7.4.18, and 8.1.6, 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. This issue affects symfony/yaml through v5.4.53, v6.0.0-BETA1 through v6.4.44, v7.0.0-BETA1 through v7.4.17, and v8.0.0-BETA1 through v8.1.5.

Last activity 15 Oct 2026. Patch Forecast updates every hour.