{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-26237 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-26237 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-26237 is a high-severity command injection vulnerability in n/a, published on 24 Aug 2026. 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-26237 and fix it if it is affected.\n\nWhat it is: CVE-2025-26237 is a high-severity command injection vulnerability in n/a, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-26237 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-26237/ (Markdown: https://insights.sbomify.com/CVE-2025-26237/index.md)","id":"CVE-2025-26237","markdown":"https://insights.sbomify.com/CVE-2025-26237/index.md","name":"CVE-2025-26237","record":{"aliases":["GHSA-9p6g-3qxg-62hh"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"D-Link 5G router","requires_auth":"none","summary":"Attackers can execute arbitrary commands on D-Link DI-7001 MINI_5G routers via the msp_info flag parameter.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"D-Link DI-7001 MINI_5G 19.10.31A1 contains a code execution vulnerability in the flag parameter of msp_info, which can be exploited to run arbitrary commands.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2025-26237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2025-26238"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-26216"},"products":["n/a"],"published":"2026-08-24","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands on D-Link DI-7001 MINI_5G routers via the msp_info flag parameter.","url":"https://insights.sbomify.com/CVE-2025-26237/"}