{"answers":{"affected":"2 open source packages ship an affected version, including elysia.","exploited":"There is no known exploitation of CVE-2026-56669 in the wild and no public exploit code.","fix":"Upgrade elysia to 1.4.29 or later.","what":"CVE-2026-56669 is a high-severity denial of service vulnerability in elysiajs elysia, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56669 and fix it if it is affected.\n\nWhat it is: CVE-2026-56669 is a high-severity denial of service vulnerability in elysiajs elysia, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56669 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- elysia (npm): affected all versions; fixed in 1.4.29\n- elysia (npm): affected all versions; fixed in 1.4.29\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-56669/ (Markdown: https://insights.sbomify.com/CVE-2026-56669/index.md)","id":"CVE-2026-56669","markdown":"https://insights.sbomify.com/CVE-2026-56669/index.md","name":"CVE-2026-56669","record":{"aliases":["GHSA-9643-4qgh-g8mx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TypeScript web framework","requires_auth":"none","summary":"Attackers can cause CPU exhaustion in Elysia applications by sending multipart requests with many unique keys, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"},{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"Elysia is a Typescript framework for request validation, type inference, OpenAPI documentation, and client-server communication. Prior to 1.4.29, Elysia uses getAll in form data normalization for multipart/form-data endpoints, causing the amount of work to grow quadratically with the number of unique key-value pairs and allowing CPU exhaustion. This issue is fixed in version 1.4.29.","ecosystems":["npm"],"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":"Elysia: Inefficient Algorithmic Complexity and Interpretation Conflict","id":"CVE-2026-56669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"ComfyUI: Stored XSS via SVG file upload on the /view endpoint","id":"CVE-2026-56670"},"packages":[{"ecosystem":"npm","fixed":["1.4.29"],"introduced":["0"],"last_affected":[],"package":"elysia","purl":null,"source":"GHSA-9643-4qgh-g8mx"},{"ecosystem":"npm","fixed":["1.4.29"],"introduced":["0"],"last_affected":[],"package":"elysia","purl":"pkg:npm/elysia","source":"GHSA-9643-4qgh-g8mx"}],"prev":{"headline":"ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange","id":"CVE-2026-56668"},"products":["elysia"],"published":"2026-07-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-07-10","vendors":["elysiajs"]},"summary":"Attackers can cause CPU exhaustion in Elysia applications by sending multipart requests with many unique keys, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-56669/"}