{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60691 exists.","fix":"No fix has been published for CVE-2025-60691 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60691 is a high-severity memory corruption vulnerability in n/a, published on 13 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-60691 and fix it if it is affected.\n\nWhat it is: CVE-2025-60691 is a high-severity memory corruption vulnerability in n/a, published on 13 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60691 exists.\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-60691/ (Markdown: https://insights.sbomify.com/CVE-2025-60691/index.md)","id":"CVE-2025-60691","markdown":"https://insights.sbomify.com/CVE-2025-60691/index.md","name":"CVE-2025-60691","record":{"aliases":["GHSA-fgwp-pq6g-c2g2"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linksys router firmware","requires_auth":"none","summary":"Remote attackers can execute arbitrary code or cause denial of service on Linksys E1200 v2 routers via crafted HTTP requests due to a stack-based buffer overflow.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"e1200_firmware","vendor":"linksys"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A stack-based buffer overflow exists in the httpd binary of Linksys E1200 v2 routers (Firmware E1200_v2.0.11.001_us.tar.gz). The apply_cgi and block_cgi functions copy user-supplied input from the \"url\" CGI parameter into stack buffers (v36, v29) using sprintf without bounds checking. Because these buffers are allocated as single-byte variables, any non-empty input will trigger a buffer overflow. Remote attackers can exploit this vulnerability via crafted HTTP requests to execute arbitrary code or cause denial of service without authentication.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2025-60691","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-60692"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-60690"},"products":["n/a"],"published":"2025-11-13","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-38555","kev_date_added":null,"published":"2022-08-28"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2025-60690","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2025-60692","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2025-60694","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":7.2,"headline":"Command injection in ESeries E1200","id":"CVE-2018-3953","kev_date_added":null,"published":"2018-10-17"},{"cvss_score":7.2,"headline":"Command injection in ESeries E1200","id":"CVE-2018-3954","kev_date_added":null,"published":"2018-10-17"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code or cause denial of service on Linksys E1200 v2 routers via crafted HTTP requests due to a stack-based buffer overflow.","url":"https://insights.sbomify.com/CVE-2025-60691/"}