{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-67673 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-67673 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67673 is a medium-severity memory corruption vulnerability in n/a, published on 3 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-2026-67673 and fix it if it is affected.\n\nWhat it is: CVE-2026-67673 is a medium-severity memory corruption vulnerability in n/a, published on 3 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-2026-67673 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-2026-67673/ (Markdown: https://insights.sbomify.com/CVE-2026-67673/index.md)","id":"CVE-2026-67673","markdown":"https://insights.sbomify.com/CVE-2026-67673/index.md","name":"CVE-2026-67673","record":{"aliases":["GHSA-whc8-rqfv-v7r9"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OreSat Firmware","requires_auth":"none","summary":"An attacker with physical UART access can execute arbitrary code via a stack buffer overflow in the firmware's EDL command handler.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A stack-based buffer overflow vulnerability exists in the cmd_edl function of OreSat Firmware v1.0. The vulnerability is triggered when processing the edl fw_flash command, where the \u003cfilename\u003e argument is copied to a 64-byte stack buffer via memcpy without proper length validation. An attacker with physical access to the UART3 serial interface can exploit this vulnerability by sending a maliciously crafted command with an oversized filename parameter,","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":"Memory corruption in n/a","id":"CVE-2026-67673","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2026-67678"},"packages":[],"prev":{"headline":"Microsoft SQL Server Information Disclosure Vulnerability","id":"CVE-2026-67648"},"products":["n/a"],"published":"2026-08-03","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":"partial"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["n/a"]},"summary":"An attacker with physical UART access can execute arbitrary code via a stack buffer overflow in the firmware's EDL command handler.","url":"https://insights.sbomify.com/CVE-2026-67673/"}