{"answers":{"affected":"3 open source packages ship an affected version, including tornado. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-67726 in the wild and no public exploit code.","fix":"Upgrade tornado to 6.5.3 or later.","what":"CVE-2025-67726 is a high-severity vulnerability in tornadoweb tornado, published on 12 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2025-67726 and fix it if it is affected.\n\nWhat it is: CVE-2025-67726 is a high-severity vulnerability in tornadoweb tornado, published on 12 Dec 2025. \nExploitation: There is no known exploitation of CVE-2025-67726 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tornado (PyPI): affected all versions; fixed in 6.5.3\n- tornado (PyPI): affected all versions; fixed in 6.5.3\n- tornado (PyPI): affected all versions; fixed in 6.5.3\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-2025-67726/ (Markdown: https://insights.sbomify.com/CVE-2025-67726/index.md)","id":"CVE-2025-67726","markdown":"https://insights.sbomify.com/CVE-2025-67726/index.md","name":"CVE-2025-67726","record":{"aliases":["BELL-CVE-2025-67726","DEBIAN-CVE-2025-67726","ECHO-43db-f673-83aa","GHSA-jhmp-mqwm-3gq8","MINI-f2p2-gf63-phgv","MINI-vrpm-vq8p-c7rh","OESA-2025-2881","OESA-2026-1018","PYSEC-2025-267","UBUNTU-CVE-2025-67726"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"tornado","vendor":"tornadoweb"}],"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-834","name":"Excessive Iteration"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Tornado is a Python web framework and asynchronous networking library. Versions 6.5.2 and below use an inefficient algorithm when parsing parameters for HTTP header values, potentially causing a DoS. The _parseparam function in httputil.py is used to parse specific HTTP header values, such as those in multipart/form-data and repeatedly calls string.count() within a nested loop while processing quoted semicolons. If an attacker sends a request with a large number of maliciously crafted parameters in a Content-Disposition header, the server's CPU usage increases quadratically (O(n²)) during parsing. Due to Tornado's single event loop architecture, a single malicious request can cause the entire server to become unresponsive for an extended period. This issue is fixed in version 6.5.3.","ecosystems":["PyPI"],"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":"Tornado is Vulnerable to Quadratic DoS via Crafted Multipart Parameters","id":"CVE-2025-67726","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Parse Server GitHub CI workflow vulnerable to RCE through Improper Privilege Management","id":"CVE-2025-67727"},"packages":[{"ecosystem":"PyPI","fixed":["6.5.3"],"introduced":["0"],"last_affected":[],"package":"tornado","purl":null,"source":"GHSA-jhmp-mqwm-3gq8"},{"ecosystem":"PyPI","fixed":["6.5.3"],"introduced":["0"],"last_affected":[],"package":"tornado","purl":"pkg:pypi/tornado","source":"GHSA-jhmp-mqwm-3gq8"},{"ecosystem":"PyPI","fixed":["6.5.3"],"introduced":["0"],"last_affected":[],"package":"tornado","purl":"pkg:pypi/tornado","source":"PYSEC-2025-267"}],"prev":{"headline":"Tornado is Vulnerable to Quadratic DoS via Repeated Header Coalescing","id":"CVE-2025-67725"},"products":["tornado"],"published":"2025-12-12","related":[{"cvss_score":8.7,"headline":"Tornado has a DoS due to too many multipart parts","id":"CVE-2026-31958","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":7.5,"headline":"Tornado is Vulnerable to Quadratic DoS via Repeated Header Coalescing","id":"CVE-2025-67725","kev_date_added":null,"published":"2025-12-12"},{"cvss_score":7.5,"headline":"Tornado has HTTP cookie parsing DoS vulnerability","id":"CVE-2024-52804","kev_date_added":null,"published":"2024-11-22"},{"cvss_score":7.2,"headline":"Tornado has incomplete validation of cookie attributes","id":"CVE-2026-35536","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":6.5,"headline":"Tornado XSRF cookie allows side-channel attack against TLS (BREACH attack)","id":"CVE-2014-9720","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":6.1,"headline":"Open redirect in Tornado","id":"CVE-2023-28370","kev_date_added":null,"published":"2023-05-25"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2025-12-18","vendors":["tornadoweb"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-67726/"}