cve.bz

CVE-2026-109413 Uncontrolled Recursion

8.7 highEPSS 0.4%Fix available

High (8.7). EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in symfony/symfony 5.4.54, 6.4.45, 7.4.18.

On this page
In Symfony YAML prior to versions 5.4.54, 6.4.45, 7.4.18, and 8.1.6, Yaml\Parser::lexInlineStructure() recursed through lexInlineMapping() and lexInlineSequence() for every { and [ of an inline collection, without entering the nesting level that the rest of the parser bounds with maxNestingLevel. A document made of deeply nested inline collections, such as [[[[...]]]], exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error. Any code parsing untrusted YAML is affected. 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 is enough. This issue affects symfony/yaml through v5.4.53, v6.0.0-BETA1 through v6.4.44, v7.0.0-BETA1 through v7.4.17, and v8.0.0-BETA1 through v8.1.5.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-674 Uncontrolled Recursion
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • symfony/symfony (Packagist): fixed in 5.4.54, 6.4.45, 7.4.18, 8.1.6
  • symfony/yaml (Packagist): fixed in 5.4.54, 6.4.45, 7.4.18, 8.1.6
  • Debian: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-109413 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109413?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109413?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109413 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2v3c-qxhr-7vpvPackagistsymfony/symfony>=2.0.0 <5.4.545.4.54
GHSA-2v3c-qxhr-7vpvPackagistsymfony/symfony>=6.0.0 <6.4.456.4.45
GHSA-2v3c-qxhr-7vpvPackagistsymfony/symfony>=7.0.0 <7.4.187.4.18
GHSA-2v3c-qxhr-7vpvPackagistsymfony/symfony>=8.0.0 <8.1.68.1.6
GHSA-2v3c-qxhr-7vpvPackagistsymfony/yaml>=2.0.0 <5.4.545.4.54
GHSA-2v3c-qxhr-7vpvPackagistsymfony/yaml>=6.0.0 <6.4.456.4.45
GHSA-2v3c-qxhr-7vpvPackagistsymfony/yaml>=7.0.0 <7.4.187.4.18
GHSA-2v3c-qxhr-7vpvPackagistsymfony/yaml>=8.0.0 <8.1.68.1.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12symfonyno fix listedDEBIAN-CVE-2026-109413
Debian13symfony6.4.49+dfsg-0+deb13u1DEBIAN-CVE-2026-109413
Debian14symfony7.4.18+dfsg-1DEBIAN-CVE-2026-109413
Ubuntu16.04:LTS, 26.04:LTS, 26.10 and 4 moresymfonyno fix listedUBUNTU-CVE-2026-109413

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON