{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100604 is a medium-severity missing authorization vulnerability in openclaw clawhub, published on 26 Sep 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-100604 and fix it if it is affected.\n\nWhat it is: CVE-2026-100604 is a medium-severity missing authorization vulnerability in openclaw clawhub, published on 26 Sep 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-100604 in the wild and no public exploit code.\n\nAffected product: openclaw clawhub. 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-100604/ (Markdown: https://insights.sbomify.com/CVE-2026-100604/index.md)","id":"CVE-2026-100604","markdown":"https://insights.sbomify.com/CVE-2026-100604/index.md","name":"CVE-2026-100604","record":{"aliases":["GHSA-7q3h-63x4-wqwg","GHSA-9558-q4f9-324f"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ClawHub skill registry","requires_auth":"low_privilege","summary":"Former publishers can retain control over organization-owned skills, allowing unauthorized transfer, deletion, or restoration of trusted skills.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"ClawHub (openclaw/clawhub) contains an incorrect authorization vulnerability in the ClawHub application/backend: an organization-owned skill retains the ownerUserId of its original publisher, and transfer and lifecycle authorization checks trust that historical user before requiring current organization privileges. An authenticated user who originally published an organization skill can therefore transfer, delete, or restore that skill — taking control of its trusted name and history — even after their organization privileges have been revoked or downgraded. The issue was confirmed at revision cbfee7343ddc867316dd9b3de6fa8856730f9f41; the complete historical affected range was not established. It is fixed by PR #3680, included in revision 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650, which was deployed to clawhub.ai on 2026-09-11; self-hosted deployments should update to that revision or a later descendant. The npm CLI and OpenClaw runtime are separate products and are not affected.","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":"ClawHub Authentication Bypass via Former Publisher Skill Control","id":"CVE-2026-100604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Flowise through 3.1.4 Missing Authorization via Chat Message Routes","id":"CVE-2026-100605"},"packages":[],"prev":{"headline":"ClawHub before 8c2de6c506 Skill Hiding via Coordinated Reports","id":"CVE-2026-100603"},"products":["clawhub"],"published":"2026-09-26","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["openclaw"]},"summary":"Former publishers can retain control over organization-owned skills, allowing unauthorized transfer, deletion, or restoration of trusted skills.","url":"https://insights.sbomify.com/CVE-2026-100604/"}