{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-67961 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-67961 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67961 is a high-severity code injection vulnerability in n/a, published on 17 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-67961 and fix it if it is affected.\n\nWhat it is: CVE-2026-67961 is a high-severity code injection vulnerability in n/a, published on 17 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-67961 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-67961/ (Markdown: https://insights.sbomify.com/CVE-2026-67961/index.md)","id":"CVE-2026-67961","markdown":"https://insights.sbomify.com/CVE-2026-67961/index.md","name":"CVE-2026-67961","record":{"aliases":["GHSA-8h87-jxwq-c68v"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"O2OA application","requires_auth":"low_privilege","summary":"A local attacker can execute arbitrary code in O2OA by exploiting the sandbox mechanism of the Invoke script execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"An issue in O2OA v.10.0.2 allows a local attacker to execute arbitrary code via the the sandbox mechanism of the Invoke script execution.","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":"Code injection in n/a","id":"CVE-2026-67961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2026-67965"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2026-67960"},"products":["n/a"],"published":"2026-08-17","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-18","vendors":["n/a"]},"summary":"A local attacker can execute arbitrary code in O2OA by exploiting the sandbox mechanism of the Invoke script execution.","url":"https://insights.sbomify.com/CVE-2026-67961/"}