{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-0830 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0830 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0830 is a high-severity command injection vulnerability in AWS Kiro IDE, published on 9 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-0830 and fix it if it is affected.\n\nWhat it is: CVE-2026-0830 is a high-severity command injection vulnerability in AWS Kiro IDE, published on 9 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-0830 in the wild and no public exploit code.\n\nAffected product: AWS Kiro IDE. 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-0830/ (Markdown: https://insights.sbomify.com/CVE-2026-0830/index.md)","id":"CVE-2026-0830","markdown":"https://insights.sbomify.com/CVE-2026-0830/index.md","name":"CVE-2026-0830","record":{"aliases":["GHSA-7xjv-wf6r-872r"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Kiro IDE","requires_auth":"none","summary":"Attackers can execute arbitrary commands by tricking users into opening maliciously crafted workspaces in Kiro IDE.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[{"product":"kiro_ide","vendor":"amazon"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Processing specially crafted workspace folder names could allow for arbitrary command injection in the Kiro GitLab Merge-Request helper in Kiro IDE before version 0.6.18 when opening maliciously crafted workspaces.\n\nTo mitigate, users should update to the latest version.","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 Kiro GitLab Merge Request Helper","id":"CVE-2026-0830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Templately \u003c= 3.4.8 - Unauthenticated Limited Arbitrary JSON File Write","id":"CVE-2026-0831"},"packages":[],"prev":{"headline":"Frontend File Manager Plugin \u003c= 23.5 - Unauthenticated Arbitrary Email Sending","id":"CVE-2026-0829"},"products":["Kiro IDE"],"published":"2026-01-09","related":[{"cvss_score":8.6,"headline":"Kiro IDE Insufficient File Write Restrictions to Execution-Sensitive Paths","id":"CVE-2026-10591","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":8.5,"headline":"Executable Resolution from Untrusted Project Directory in Kiro IDE on Windows","id":"CVE-2026-18656","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":6.7,"headline":"Kiro IDE Sensitive Workspace Data Exfiltration via Agent-Written Workspace Configuration","id":"CVE-2026-89332","kev_date_added":null,"published":"2026-09-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-09","vendors":["AWS"]},"summary":"Attackers can execute arbitrary commands by tricking users into opening maliciously crafted workspaces in Kiro IDE.","url":"https://insights.sbomify.com/CVE-2026-0830/"}