{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81837 exists.","fix":"No fix has been published for CVE-2026-81837 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81837 is a medium-severity path traversal vulnerability in RooCodeInc Roo-Code, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-81837 and fix it if it is affected.\n\nWhat it is: CVE-2026-81837 is a medium-severity path traversal vulnerability in RooCodeInc Roo-Code, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81837 exists.\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-2026-81837/ (Markdown: https://insights.sbomify.com/CVE-2026-81837/index.md)","id":"CVE-2026-81837","markdown":"https://insights.sbomify.com/CVE-2026-81837/index.md","name":"CVE-2026-81837","record":{"aliases":["GHSA-pjx2-9jx7-x89r"],"analysis":{"component_type":"developer_tool","fix_type":"end_of_life","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Roo Code AI assistant","requires_auth":"none","summary":"Remote attackers can exploit path traversal in Roo Code's ApplyPatchTool to read or modify arbitrary files, affecting an unsupported project.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A flaw has been found in RooCodeInc Roo-Code up to 3.51.1. This issue affects the function path.resolve of the file src/core/tools/ApplyPatchTool.ts of the component ApplyPatchTool. This manipulation causes path traversal. It is possible to initiate the attack remotely. The exploit has been published and may be used. Multiple isses were reported to the vendor beforehand. They explain, that \"they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it.\" This vulnerability only affects products that are no longer supported by the maintainer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"RooCodeInc Roo-Code ApplyPatchTool ApplyPatchTool.ts path.resolve path traversal","id":"CVE-2026-81837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Zip Slip Arbitrary File Write in AWS diagram-as-code (awsdac)","id":"CVE-2026-81838"},"packages":[],"prev":{"headline":"RooCodeInc Roo-Code OAuth Callback oauth.ts cleartext transmission","id":"CVE-2026-81836"},"products":["Roo-Code"],"published":"2026-08-27","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["RooCodeInc"]},"summary":"Remote attackers can exploit path traversal in Roo Code's ApplyPatchTool to read or modify arbitrary files, affecting an unsupported project.","url":"https://insights.sbomify.com/CVE-2026-81837/"}