GHSA-c2p3-7m5p-cv8x

Symfony hardened the parser when handling untrusted input

At a glance

Published
Updated
CVE
CVE-2026-45133
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U

Description

### Description `Symfony\Component\Yaml\Parser` is the entry point for parsing YAML strings into PHP values via `Yaml::parse()`. When the parser is exposed to attacker-controlled input, deeply nested mappings or sequences cause both the block-level (`Parser::parseBlock()`) and inline (`Inline::parseSequence()` / `Inline::parseMapping()`) parsers to recurse without a depth limit. A crafted document exhausts the PHP stack and crashes the worker. ### Resolution The `Parser` now tracks recursion depth in a shared `ParserState` object across both block-level and inline parsing, with a default limit of **128**. The limit is configurable via a new `$maxNestingLevel` argument on `Parser::__construct()`, `Yaml::parse()` and `Yaml::parseFile()`. The patch for this issue is available [here](https://github.com/symfony/symfony/commit/914f427ed9630ddb3904dafba763e53d9f133fe3) for branch 5.4. ### Credits Symfony would like to thank Pietro Tirenna (Shielder) for reporting the issue and Nicolas Grekas for fixing it.

Affected packages

PackageVersions
Packagist · symfony/yamlintroduced 0, fixed 5.4.52
Packagist · symfony/symfonyintroduced 0, fixed 5.4.52
Packagist · symfony/symfonyintroduced 6.0.0, fixed 6.4.40
Packagist · symfony/symfonyintroduced 7.0.0, fixed 7.4.12
Packagist · symfony/symfonyintroduced 8.0.0, fixed 8.0.12
Packagist · symfony/yamlintroduced 6.0.0, fixed 6.4.40
Packagist · symfony/yamlintroduced 7.0.0, fixed 7.4.12
Packagist · symfony/yamlintroduced 8.0.0, fixed 8.0.12

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database