-
-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency symfony/yaml to 5.4.* [SECURITY] - #36
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Author
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: composer.lock
Command failed: composer install --ignore-platform-req=ext-* --ignore-platform-req=lib-* --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- laminas/laminas-code is locked to version 4.4.2 and an update of this package was not requested.
- laminas/laminas-code 4.4.2 requires php ^7.4 || ~8.0.0 -> your php version (8.5.9) does not satisfy that requirement.
Problem 2
- php-amqplib/php-amqplib is locked to version v2.12.3 and an update of this package was not requested.
- php-amqplib/php-amqplib v2.12.3 requires php >=5.6.3,<8.0 -> your php version (8.5.9) does not satisfy that requirement.
Problem 3
- clivern/chunk is locked to version 2.0.1 and an update of this package was not requested.
- clivern/chunk 2.0.1 requires php-amqplib/php-amqplib ^2.11 -> satisfiable by php-amqplib/php-amqplib[v2.12.3].
- php-amqplib/php-amqplib v2.12.3 requires php >=5.6.3,<8.0 -> your php version (8.5.9) does not satisfy that requirement.
Tick the box to add this pull request to the merge queue (same as @mergifyio queue).
- Queue this pull request
1 similar comment
Tick the box to add this pull request to the merge queue (same as @mergifyio queue).
- Queue this pull request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
This PR contains the following updates:
5.2.*→5.4.*Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Symfony hardened the parser when handling untrusted input
CVE-2026-45133 / GHSA-c2p3-7m5p-cv8x
More information
Details
Description
Symfony\Component\Yaml\Parseris the entry point for parsing YAML strings into PHP values viaYaml::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
Parsernow tracks recursion depth in a sharedParserStateobject across both block-level and inline parsing, with a default limit of 128. The limit is configurable via a new$maxNestingLevelargument onParser::__construct(),Yaml::parse()andYaml::parseFile().The patch for this issue is available here for branch 5.4.
Credits
Symfony would like to thank Pietro Tirenna (Shielder) for reporting the issue and Nicolas Grekas for fixing it.
Severity
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:UReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Symfony's YAML Parser Vulnerable to Exponential Memory Allocation via Recursive Collection-Alias Expansion ("Billion Laughs")
CVE-2026-45304 / GHSA-4qpc-3hr4-r2p4
More information
Details
Description
Symfony\Component\Yaml\Parserresolves YAML aliases (*anchor) during parsing. Aliases that reference collections (arrays,stdClass,TaggedValue-wrapped collections) can themselves point to other collections containing aliases, creating exponential expansion at resolution time. A small input can blow up into a multi-gigabyte structure and exhaust memory: the classic "Billion Laughs" denial-of-service against any parser exposed to untrusted YAML.Resolution
The
Parsernow counts collection alias resolutions in a sharedParserStateobject, with a default limit of 128, following the SnakeYAML model. Scalar aliases remain unrestricted since they cannot drive exponential growth. The limit is configurable via a new$maxAliasesForCollectionsargument onParser::__construct(),Yaml::parse()andYaml::parseFile(). A newYaml::PARSE_EXCEPTION_ON_ALIASflag also rejects all aliases outright when parsing fully untrusted input.The patch for this issue is available here for branch 5.4.
Credits
Symfony would like to thank Pietro Tirenna (Shielder) for reporting the issue and Nicolas Grekas for fixing it.
Severity
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:UReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Symfony's YAML Parser has a ReDoS via Catastrophic Backtracking in Parser::cleanup() Regex
CVE-2026-45305 / GHSA-9frc-8383-795m
More information
Details
Description
Symfony\Component\Yaml\Parser::cleanup()strips the optional%YAMLdirective header, leading comments, and document start/end markers before parsing. The original regexes contained overlapping quantifiers, most notably'#^%YAML[: ][\d.]+.*\n#u', whose[\d.]+and.*overlap on the dot, that exhibit catastrophic backtracking on crafted input. A single oversized%YAMLdirective header (or comment / document-marker line) makes the parser hang for an arbitrarily long time, denying service.Resolution
The four regexes in
Parser::cleanup()(YAML directive header, leading comments, document-start marker, document-end marker) have been rewritten with possessive quantifiers and unambiguous character classes so backtracking cannot occur.The patch for this issue is available here for branch 5.4.
Credits
Symfony would like to thank Pietro Tirenna (Shielder) for reporting the issue and Nicolas Grekas for fixing it.
Severity
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:UReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
symfony/yaml (symfony/yaml)
v5.4.52Compare Source
Changelog (symfony/yaml@v5.4.44...v5.4.52)
v5.4.45Compare Source
Changelog (symfony/yaml@v5.4.44...v5.4.45)
v5.4.44Compare Source
Changelog (symfony/yaml@v5.4.43...v5.4.44)
v5.4.43Compare Source
Changelog (symfony/yaml@v5.4.42...v5.4.43)
v5.4.40Compare Source
Changelog (symfony/yaml@v5.4.39...v5.4.40)
v5.4.39Compare Source
Changelog (symfony/yaml@v5.4.38...v5.4.39)
v5.4.35Compare Source
Changelog (symfony/yaml@v5.4.34...v5.4.35)
v5.4.31Compare Source
Changelog (symfony/yaml@v5.4.30...v5.4.31)
v5.4.30Compare Source
Changelog (symfony/yaml@v5.4.29...v5.4.30)
v5.4.23Compare Source
Changelog (symfony/yaml@v5.4.22...v5.4.23)
v5.4.21Compare Source
Changelog (symfony/yaml@v5.4.20...v5.4.21)
v5.4.19Compare Source
Changelog (symfony/yaml@v5.4.18...v5.4.19)
v5.4.17Compare Source
Changelog (symfony/yaml@v5.4.16...v5.4.17)
v5.4.16Compare Source
Changelog (symfony/yaml@v5.4.15...v5.4.16)
v5.4.14Compare Source
Changelog (symfony/yaml@v5.4.13...v5.4.14)
v5.4.12Compare Source
Changelog (symfony/yaml@v5.4.11...v5.4.12)
v5.4.11Compare Source
Changelog (symfony/yaml@v5.4.10...v5.4.11)
v5.4.10Compare Source
Changelog (symfony/yaml@v5.4.9...v5.4.10)
v5.4.3Compare Source
Changelog (symfony/yaml@v5.4.2...v5.4.3)
v5.4.2Compare Source
Changelog (symfony/yaml@v5.4.1...v5.4.2)
v5.4.0Compare Source
Changelog (symfony/yaml@v5.4.0-RC1...v5.4.0)
v5.3.14Compare Source
Changelog (symfony/yaml@v5.3.13...v5.3.14)
v5.3.13Compare Source
Changelog (symfony/yaml@v5.3.12...v5.3.13)
v5.3.11Compare Source
Changelog (symfony/yaml@v5.3.10...v5.3.11)
v5.3.6Compare Source
Changelog (symfony/yaml@v5.3.5...v5.3.6)
v5.3.4Compare Source
Changelog (symfony/yaml@v5.3.3...v5.3.4)
v5.3.3Compare Source
Changelog (symfony/yaml@v5.3.2...v5.3.3)
v5.3.2Compare Source
Changelog (symfony/yaml@v5.3.1...v5.3.2)
v5.3.0Compare Source
Changelog (symfony/yaml@v5.3.0-RC1...v5.3.0)
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.