CVE-2026-45304: Symfony Yaml denial of service via recursive alias expansion

CVE-2026-45304 · Severity: medium · CVSS 4 · Published 2026-07-14

A vulnerability in the Symfony PHP framework's YAML processing component could allow an attacker to crash a web application. By submitting a specially crafted, small YAML file, an attacker can force the server to consume massive amounts of memory, leading to a denial-of-service (DoS) condition. This affects any application that parses untrusted YAML input using the vulnerable versions of the library.

Technologies: symfony/symfony (Packagist), symfony/yaml (Packagist), Symfony Yaml. Vendors: Packagist, Symfony.

Quick answers

Is CVE-2026-45304 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45304 being exploited in the wild.
How severe is CVE-2026-45304?
Medium severity, with a CVSS score of 4, published 14 July 2026.
Which products and versions are affected?
symfony/symfony (Packagist) ECOSYSTEM:introduced=0,fixed=5.4.52; symfony/yaml (Packagist) ECOSYSTEM:introduced=0,fixed=5.4.52; Symfony Yaml < 5.4.52, >= 6.0.0-BETA1, < 6.4.40, >= 7.0.0-BETA1, < 7.4.12, >= 8.0.0-BETA1, < 8.0.12, < 5.4.52, >= 6.0.0, < 6.4.40, >= 7.0.0, < 7.4.12, >= 8.0.0, < 8.0.12.
Is there a fix for CVE-2026-45304?
Yes. symfony/symfony (Packagist): upgrade to 5.4.52 or later; symfony/yaml (Packagist): upgrade to 5.4.52 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45304 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-45304?
Check whether you run symfony/symfony (Packagist), symfony/yaml (Packagist) or Symfony Yaml at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • symfony/symfony (Packagist): upgrade to 5.4.52 or later
    composer require symfony/symfony:^5.4.52
  • symfony/yaml (Packagist): upgrade to 5.4.52 or later
    composer require symfony/yaml:^5.4.52

Technical details

The Symfony\Component\Yaml\Parser component fails to properly restrict the number of recursive collection aliases during YAML parsing. An attacker can provide a small, crafted YAML document containing recursive aliases that expand exponentially into a multi-gigabyte structure upon resolution. This leads to memory exhaustion and a denial-of-service (DoS) condition. The vulnerability is classified as CWE-776 (Improper Restriction of Recursive Entity References). The fix introduces a default limit of 128 resolved collection aliases and adds a new flag, Yaml::PARSE_EXCEPTION_ON_ALIAS, to allow developers to reject aliases entirely when handling untrusted input. Patches are available in versions 5.4.52, 6.4.40, 7.4.12, and 8.0.12.

Affected products

  • Symfony symfony/symfony < 5.4.52, >= 6.0.0-BETA1, < 6.4.40, >= 7.0.0-BETA1, < 7.4.12, >= 8.0.0-BETA1, < 8.0.12
  • Symfony symfony/yaml < 5.4.52, >= 6.0.0-BETA1, < 6.4.40, >= 7.0.0-BETA1, < 7.4.12, >= 8.0.0-BETA1, < 8.0.12

Identifiers

  • CVE-2026-45304
  • GHSA-4qpc-3hr4-r2p4

Timeline

  • 2026-05-08: other: Initial fix authored
  • 2026-05-20: patched: Security releases published
  • 2026-07-14: advisory: NVD advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.