{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-63655 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-63655 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63655 is a high-severity vulnerability in n/a, published on 29 Jan 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-2025-63655 and fix it if it is affected.\n\nWhat it is: CVE-2025-63655 is a high-severity vulnerability in n/a, published on 29 Jan 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-2025-63655 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2025-63655/ (Markdown: https://insights.sbomify.com/CVE-2025-63655/index.md)","id":"CVE-2025-63655","markdown":"https://insights.sbomify.com/CVE-2025-63655/index.md","name":"CVE-2025-63655","record":{"aliases":["AZL-76358","AZL-76380","GHSA-9w8p-mp2m-7qp7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Monkey web server","requires_auth":"none","summary":"Attackers can cause a Denial of Service in the Monkey web server by sending a crafted HTTP request that triggers a NULL pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"monkey","vendor":"monkey-project"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-476","name":"NULL Pointer Dereference"}],"description":"A NULL pointer dereference in the mk_http_range_parse function (mk_server/mk_http.c) of monkey commit f37e984 allows attackers to cause a Denial of Service (DoS) via sending a crafted HTTP request to the server.","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":"Null dereference in n/a","id":"CVE-2025-63655","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-63656"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-63653"},"products":["n/a"],"published":"2026-01-29","related":[{"cvss_score":9.8,"headline":"Auth bypass in monkey","id":"CVE-2013-2159","kev_date_added":null,"published":"2019-12-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-63649","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-63650","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2025-63651","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2025-63652","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-63653","kev_date_added":null,"published":"2026-01-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-02-03","vendors":["n/a"]},"summary":"Attackers can cause a Denial of Service in the Monkey web server by sending a crafted HTTP request that triggers a NULL pointer dereference.","url":"https://insights.sbomify.com/CVE-2025-63655/"}