Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-123792

The Symfony Yaml componentsInlineandParser, parse some YAML documents ...

Overview

Published
6 Nov 2026
Modified
10 Nov 2026
High CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available
CVSS score High, no score

Description

The Symfony Yaml components Inline and Parser, parse some YAML documents inefficiently, so that a small crafted document can take disproportionately long to process, keeping a PHP process busy for seconds or minutes, potentially causing a denial of service in Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.

The parser repeats work it has already done in several places. An embedded mapping in a flow sequence is parsed again for every scalar appended to it, and so are the collections nested in it, so the parse time grows exponentially with the nesting depth. The patterns matching mapping keys and tags scan a run of spaces once per character of the run, and each scalar of a flow collection is matched against a copy of the rest of the collection, so the parse time grows quadratically with the size of the input. Nested blocks are also copied at each nesting level, which consumes memory as well as time. A few other constructs, such as an empty sequence item followed by a blank line or an anchor named 0, trigger similar repeated work.

Any code parsing untrusted YAML is affected, with the default flags. In Symfony 7.4 and later, 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 keeps a PHP worker busy until max_execution_time. JSON documents are valid YAML, so a JSON payload sent with a YAML content type is enough for the flow collection case. In Symfony 6.4, #[MapRequestPayload] accepts YAML only when the application registers a yaml request format.

Source: OX vulnerability database

Severity

HIGH

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-407, CWE-1333

Affected packages · 2

Packages affected by CVE-2026-123792
EcosystemPackageVulnerableFixed in
Composer (PHP) symfony/symfony >=5.2.0, <5.3.0>=5.4.0, <5.4.56>=6.4.0, <6.4.50>=7.0.0, <7.1.0>=7.4.0, <7.4.23+15 more No fix yet
Composer (PHP) symfony/yaml >=3.0.0, <4.0.0>=4.0.0, <5.0.0>=5.1.0, <5.2.0>=5.2.0, <5.3.0>=6.0.0, <6.1.0+15 more No fix yet

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

debian 4 releases · 1 package

affected 2 fixed 2
symfony
debian fixes for CVE-2026-123792
ReleasePackageFixed in
11 symfony affected
12 symfony affected
13 symfony 6.4.50+dfsg-0+deb13u1
14 symfony 7.4.23+dfsg-1

echo 1 release · 1 package

fixed 1
symfony
echo fixes for CVE-2026-123792
ReleasePackageFixed in
symfony 6.4.50+dfsg-0+deb13u1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.