{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-70085 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-70085 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70085 is a critical memory corruption vulnerability in n/a, published on 11 Feb 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-70085 and fix it if it is affected.\n\nWhat it is: CVE-2025-70085 is a critical memory corruption vulnerability in n/a, published on 11 Feb 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-70085 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-70085/ (Markdown: https://insights.sbomify.com/CVE-2025-70085/index.md)","id":"CVE-2025-70085","markdown":"https://insights.sbomify.com/CVE-2025-70085/index.md","name":"CVE-2025-70085","record":{"aliases":["GHSA-hfmq-6wjv-c7r3"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenSatKit satellite software","requires_auth":"none","summary":"A stack buffer overflow in OpenSatKit allows attackers to execute arbitrary code or cause denial of service via crafted filenames.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opensatkit","vendor":"opensatkit"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/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":"An issue was discovered in OpenSatKit 2.2.1. The EventErrStr buffer has a fixed size of 256 bytes. The code uses sprintf to format two filenames (Source1Filename and the string returned by FileUtil_FileStateStr) into this buffer without any length checking and without using bounded format specifiers such as %.*s. If the filename length approaches OS_MAX_PATH_LEN (commonly 64-256 bytes), the combined formatted string together with constant text can exceed 256 bytes, resulting in a stack buffer overflow. Such unsafe sprintf calls are scattered across multiple functions in file.c, including FILE_ConcatenateCmd() and ConcatenateFiles(), all of which fail to validate the output length.","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":"Memory corruption in n/a","id":"CVE-2025-70085","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-70091"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-70084"},"products":["n/a"],"published":"2026-02-11","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2025-70083","kev_date_added":null,"published":"2026-02-11"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2025-70084","kev_date_added":null,"published":"2026-02-11"}],"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":"total"},"state":"PUBLISHED","updated":"2026-02-12","vendors":["n/a"]},"summary":"A stack buffer overflow in OpenSatKit allows attackers to execute arbitrary code or cause denial of service via crafted filenames.","url":"https://insights.sbomify.com/CVE-2025-70085/"}