{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107820 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-107820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-107820 is a medium-severity vulnerability in duty1g x64dbg-mcp-server, published on 9 Oct 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-107820 and fix it if it is affected.\n\nWhat it is: CVE-2026-107820 is a medium-severity vulnerability in duty1g x64dbg-mcp-server, published on 9 Oct 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-107820 in the wild and no public exploit code.\n\nAffected product: duty1g x64dbg-mcp-server. 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-107820/ (Markdown: https://insights.sbomify.com/CVE-2026-107820/index.md)","id":"CVE-2026-107820","markdown":"https://insights.sbomify.com/CVE-2026-107820/index.md","name":"CVE-2026-107820","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"x64dbg MCP plugin","requires_auth":"none","summary":"Unauthenticated attackers can crash the x64dbg debugger by sending a large Content-Length header, causing a denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"x64dbg-MCP Server is a native Model Context Protocol (MCP) plugin for x64dbg that exposes the debugger's full functionality over HTTP. Prior to 1.2, src/core/mcp_server.zig parses an unbounded Content-Length value in parseContentLength() and uses it in unchecked usize addition in wsRecv() before token authentication. The server listens on 0.0.0.0 by default in affected versions. An unauthenticated network client can supply a near-maximum Content-Length value to trigger a runtime integer-overflow panic in Debug and ReleaseSafe builds, terminating the entire x64dbg process and its live debugging session. The overflowed value is used only in a comparison, so the impact is limited to denial of service rather than memory corruption or code execution. This issue is fixed in version 1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"x64dbg-MCP Server vulnerable to pre-authentication denial of service through Content-Length integer overflow","id":"CVE-2026-107820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"MariaDB: insufficient validation of binary frm data when opening a table","id":"CVE-2026-107821"},"packages":[],"prev":{"headline":"MariaDB Connector/C: libmariadb allowed cleartext password leakage on TLS hostname verification failure","id":"CVE-2026-107819"},"products":["x64dbg-mcp-server"],"published":"2026-10-09","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-10-13","vendors":["duty1g"]},"summary":"Unauthenticated attackers can crash the x64dbg debugger by sending a large Content-Length header, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-107820/"}