{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-62189 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-62189 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62189 and fix it if it is affected.\n\nWhat it is: CVE-2026-62189 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-62189 in the wild and no public exploit code.\n\nAffected product: Openclaw Openclaw. 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-62189/ (Markdown: https://insights.sbomify.com/CVE-2026-62189/index.md)","id":"CVE-2026-62189","markdown":"https://insights.sbomify.com/CVE-2026-62189/index.md","name":"CVE-2026-62189","record":{"aliases":["GHSA-m38g-vpwj-mpg9","GHSA-vgjq-7pq9-cvwp","MINI-j69g-v9r8-2vg4"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenClaw","requires_auth":"low_privilege","summary":"Attackers can bypass authorization boundaries via symlink following in the mirror sync feature, requiring the feature to be enabled.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"openclaw","vendor":"openclaw"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"OpenClaw versions before 2026.6.9 contain a symlink following vulnerability in the mirror sync feature that allows lower-trust callers to perform actions requiring stronger authorization. Attackers can exploit remote symlink parents to bypass policy checks and authorization boundaries when the feature is enabled and reachable.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OpenClaw \u003c 2026.6.9 Symlink Following via Mirror Sync","id":"CVE-2026-62189","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"openclaw:openclaw","products":["openclaw:openclaw"],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenClaw \u003c 2026.6.9 Authorization Bypass via flock wrapper","id":"CVE-2026-62190"},"packages":[],"prev":{"headline":"OpenClaw \u003c 2026.6.9 Feishu Authorization Bypass","id":"CVE-2026-62188"},"products":["OpenClaw"],"published":"2026-07-13","related":[{"cvss_score":9.9,"headline":"Security feature bypass in OpenClaw","id":"CVE-2026-28363","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2026-30741","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval","id":"CVE-2026-33579","kev_date_added":null,"published":"2026-03-31"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate","id":"CVE-2026-32922","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.11 - Approval Bypass via Unrecognized Script Runners","id":"CVE-2026-32978","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.3.12 - Scope Elevation in WebSocket Shared-Auth Connections","id":"CVE-2026-22172","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":9.4,"headline":"OpenClaw \u003c 2026.2.14 - Remote Code Execution via Node Invoke Approval Bypass","id":"CVE-2026-28466","kev_date_added":null,"published":"2026-03-05"}],"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-07-15","vendors":["OpenClaw"]},"summary":"Attackers can bypass authorization boundaries via symlink following in the mirror sync feature, requiring the feature to be enabled.","url":"https://insights.sbomify.com/CVE-2026-62189/"}