{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53097 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53097 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53097 is a medium-severity vulnerability in RooCodeInc Roo-Code, published on 27 Jun 2025. 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-53097 and fix it if it is affected.\n\nWhat it is: CVE-2025-53097 is a medium-severity vulnerability in RooCodeInc Roo-Code, published on 27 Jun 2025. 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-53097 in the wild and no public exploit code.\n\nAffected product: RooCodeInc Roo-Code. 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-53097/ (Markdown: https://insights.sbomify.com/CVE-2025-53097/index.md)","id":"CVE-2025-53097","markdown":"https://insights.sbomify.com/CVE-2025-53097/index.md","name":"CVE-2025-53097","record":{"aliases":["GHSA-wr2q-46pg-f228"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"VS Code extension","requires_auth":"none","summary":"Attackers can read sensitive files outside the workspace and leak data via JSON schema network requests if prompt injection occurs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"roo_code","vendor":"roocode"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Roo Code is an AI-powered autonomous coding agent. Prior to version 3.20.3, there was an issue where the Roo Code agent's `search_files` tool did not respect the setting to disable reads outside of the VS Code workspace. This means that an attacker who was able to inject a prompt into the agent could potentially read a sensitive file and then write the information to a JSON schema. Users have the option to disable schema fetching in VS Code, but the feature is enabled by default. For users with this feature enabled, writing to the schema would trigger a network request without the user having a chance to deny. This issue is of moderate severity, since it requires the attacker to already be able to submit prompts to the agent. Version 3.20.3 fixed the issue where `search_files` did not respect the setting to limit it to the workspace. This reduces the scope of the damage if an attacker is able to take control of the agent through prompt injection or another vector.","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":"Roo Code extension vulnerable to Potential Information Leakage via JSON Schema","id":"CVE-2025-53097","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Roo Code Vulnerable to Potential Remote Code Execution via Model Context Protocol","id":"CVE-2025-53098"},"packages":[],"prev":{"headline":"Sunshine clickjacking in the UI leads to unauthorized actions being performed","id":"CVE-2025-53096"},"products":["Roo-Code"],"published":"2025-06-27","related":[{"cvss_score":9.9,"headline":"Roo Code is vulnerable to command injection via GitHub actions workflow","id":"CVE-2025-58371","kev_date_added":null,"published":"2025-09-05"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2026-30307","kev_date_added":null,"published":"2026-03-30"},{"cvss_score":8.1,"headline":"Roo Code is Vulnerable to Potential Remote Code Execution via zsh Command Validation Bug","id":"CVE-2025-65946","kev_date_added":null,"published":"2025-11-21"},{"cvss_score":8.1,"headline":"Roo Code: Potential Remote Code Execution via Bash Parameter Expansion and Indirect Reference","id":"CVE-2025-58370","kev_date_added":null,"published":"2025-09-05"},{"cvss_score":8.1,"headline":"Roo Code: Potential Remote Code Execution via .code-workspace","id":"CVE-2025-58372","kev_date_added":null,"published":"2025-09-05"},{"cvss_score":8.1,"headline":"Roo Code allows Potential Remote Code Execution via .vscode/settings.json","id":"CVE-2025-53536","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":8.1,"headline":"Roo Code Vulnerable to Potential Remote Code Execution via Model Context Protocol","id":"CVE-2025-53098","kev_date_added":null,"published":"2025-06-27"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-06-30","vendors":["RooCodeInc"]},"summary":"Attackers can read sensitive files outside the workspace and leak data via JSON schema network requests if prompt injection occurs.","url":"https://insights.sbomify.com/CVE-2025-53097/"}