Quick answers
- Is CVE-2026-123792 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123792 being exploited in the wild.
- How severe is CVE-2026-123792?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Symfony Yaml prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, 8.x prior to 8.1.11.
- Is there a fix for CVE-2026-123792?
- Yes: fixed in Symfony Yaml 5.4.56, 6.4.50, 7.4.23, 8.1.11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123792 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123792?
- Check whether you run 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
- Fixed in: Symfony Yaml 5.4.56, 6.4.50, 7.4.23, 8.1.11
Technical details
The Symfony Yaml parser's Inline and Parser components contain algorithmic inefficiencies: embedded mappings in flow sequences are reparsed for each scalar, causing exponential time growth with nesting depth; pattern matching for keys and tags rescans whitespace quadratically; and flow collection scalars are matched against the entire remaining collection. Authentication is not required; the attack vector is any YAML parsing of untrusted input, including HTTP endpoints decorated with #[MapRequestPayload] that accept YAML content types.
Affected products
- Symfony Yaml prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, 8.x prior to 8.1.11
Timeline
- 2026-11-06: disclosed