{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123792 in the wild and no public exploit code.","exposure":"","fix":"Upgrade to a fixed version.","what":"CVE-2026-123792 is a high-severity vulnerability in sensiolabs symfony, published on 6 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123792 and fix it if it is affected.\n\nWhat it is: CVE-2026-123792 is a high-severity vulnerability in sensiolabs symfony, published on 6 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123792 in the wild and no public exploit code.\n\nAffected product: sensiolabs symfony. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-123792/ (Markdown: https://insights.sbomify.com/CVE-2026-123792/index.md)","id":"CVE-2026-123792","markdown":"https://insights.sbomify.com/CVE-2026-123792/index.md","name":"CVE-2026-123792","record":{"aliases":["DEBIAN-CVE-2026-123792","GHSA-hwfg-qwvh-2wfx","UBUNTU-CVE-2026-123792"],"analysis":null,"analysis_generated_by":null,"assigner":"Checkmarx","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"},{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"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.\n\nThe 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.\n\nAny 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Symfony: Exponential and Quadratic Parse Times in the YAML Parser Let a Single Document Hold a Process","id":"CVE-2026-123792","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`","id":"CVE-2026-123796"},"nickname":null,"packages":[],"prev":{"headline":"OpenBMB Internet of Agents Agent Registry milvus_utils.py _primary_field_query data query logic injection","id":"CVE-2026-123791"},"products":["symfony"],"published":"2026-11-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-10","vendors":["sensiolabs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123792/"}