{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77357 exists.","fix":"No fix has been published for CVE-2026-77357 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77357 is a high-severity denial of service vulnerability in mesop-dev mesop, published on 25 Aug 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-77357 and fix it if it is affected.\n\nWhat it is: CVE-2026-77357 is a high-severity denial of service vulnerability in mesop-dev mesop, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77357 exists.\n\nAffected product: mesop-dev mesop. 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-77357/ (Markdown: https://insights.sbomify.com/CVE-2026-77357/index.md)","id":"CVE-2026-77357","markdown":"https://insights.sbomify.com/CVE-2026-77357/index.md","name":"CVE-2026-77357","record":{"aliases":["GHSA-8p72-497j-83mx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Python UI framework","requires_auth":"none","summary":"An unauthenticated attacker can crash the Mesop server by exhausting worker threads via the hot-reload endpoint in debug mode.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","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-834","name":"Excessive Iteration"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Mesop is a Python-based UI framework that allows users to build web applications. Prior to 1.3.3, applications running in debug mode expose a GET /hot-reload endpoint whose unbounded loop depends on the user-supplied counter parameter, allowing an unauthenticated attacker to hold worker threads with high counter values until the worker pool is exhausted and the server becomes unavailable. A single unauthenticated attacker can crash the Mesop server with minimal effort. Because the attack leverages worker exhaustion, the server remains unresponsive until it is manually restarted. This issue is fixed in version 1.3.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Mesop: DoS in /hot-reload endpoint allows unauthenticated attacker to exhaust worker threads and crash the server","id":"CVE-2026-77357","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"cpp-httplib: Use-after-free of TLS session in WebSocketClient::shutdown_and_close()","id":"CVE-2026-77358"},"packages":[],"prev":{"headline":"kin-openapi: Uncontrolled resource consumption in openapi3filter deepObject query parameter decoding","id":"CVE-2026-77354"},"products":["mesop"],"published":"2026-08-25","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["mesop-dev"]},"summary":"An unauthenticated attacker can crash the Mesop server by exhausting worker threads via the hot-reload endpoint in debug mode.","url":"https://insights.sbomify.com/CVE-2026-77357/"}