{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-30311 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-30311 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-30311 is a critical command injection vulnerability in n/a, published on 31 Mar 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-2026-30311 and fix it if it is affected.\n\nWhat it is: CVE-2026-30311 is a critical command injection vulnerability in n/a, published on 31 Mar 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-2026-30311 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-30311/ (Markdown: https://insights.sbomify.com/CVE-2026-30311/index.md)","id":"CVE-2026-30311","markdown":"https://insights.sbomify.com/CVE-2026-30311/index.md","name":"CVE-2026-30311","record":{"aliases":["GHSA-27rm-rrv9-67mv"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Ridvay Code CLI","requires_auth":"none","summary":"Attackers can execute arbitrary OS commands by bypassing the auto-approval whitelist via shell substitution in Ridvay Code.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"auto-approval_module","vendor":"ridvay"}],"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-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Ridvay Code's command auto-approval module contains a critical OS command injection vulnerability that renders its whitelist security mechanism completely ineffective. The system relies on fragile regular expressions to parse command structures; while it attempts to intercept dangerous operations, it fails to account for standard Shell command substitution Ridvay Code (specifically$(...)and backticks ...). An attacker can construct a command such as git log --grep=\"$(malicious_command)\", forcing Syntx to misidentify it as a safe git operation and automatically approve it. The underlying Shell prioritizes the execution of the malicious code injected within the arguments, resulting in Remote Code Execution without any user interaction.","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-2026-30311","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":"Command injection in n/a","id":"CVE-2026-30312"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2026-30310"},"products":["n/a"],"published":"2026-03-31","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2026-30314","kev_date_added":null,"published":"2026-03-31"}],"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-04-01","vendors":["n/a"]},"summary":"Attackers can execute arbitrary OS commands by bypassing the auto-approval whitelist via shell substitution in Ridvay Code.","url":"https://insights.sbomify.com/CVE-2026-30311/"}