{"answers":{"affected":"4 open source packages ship an affected version, including openclaw and clawdbot. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-28480 in the wild and no public exploit code.","fix":"Upgrade openclaw to 2026.2.14 or later.","what":"CVE-2026-28480 is a medium-severity authentication bypass vulnerability in Openclaw Openclaw, published on 5 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-28480 and fix it if it is affected.\n\nWhat it is: CVE-2026-28480 is a medium-severity authentication bypass vulnerability in Openclaw Openclaw, published on 5 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-28480 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openclaw (npm): affected all versions; fixed in 2026.2.14\n- openclaw (npm): affected all versions; fixed in 2026.2.14\n- clawdbot (npm): affected all versions up to 2026.1.24-3; no fix listed\n- clawdbot (npm): affected all versions up to 2026.1.24-3; no fix listed\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-28480/ (Markdown: https://insights.sbomify.com/CVE-2026-28480/index.md)","id":"CVE-2026-28480","markdown":"https://insights.sbomify.com/CVE-2026-28480/index.md","name":"CVE-2026-28480","record":{"aliases":["GHSA-mj5r-hh7j-4gxf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenClaw Telegram bot","requires_auth":"none","summary":"Attackers can bypass Telegram allowlist restrictions by spoofing identities using recycled usernames, allowing unauthorized interaction with bots.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"openclaw","vendor":"openclaw"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"OpenClaw versions prior to 2026.2.14 contain an authorization bypass vulnerability where Telegram allowlist matching accepts mutable usernames instead of immutable numeric sender IDs. Attackers can spoof identity by obtaining recycled usernames to bypass allowlist restrictions and interact with bots as unauthorized senders.","ecosystems":["npm"],"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.2.14 - Identity Spoofing via Mutable Username in Telegram Allowlist Authorization","id":"CVE-2026-28480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"openclaw:openclaw","products":["openclaw:openclaw"],"type":"auth_bypass","year":"2026"},"n_packages":4,"n_references":4,"next":{"headline":"OpenClaw \u003c 2026.2.1 - Bearer Token Leakage via MS Teams Attachment Downloader Suffix Matching","id":"CVE-2026-28481"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2026.1.24-3"],"package":"clawdbot","purl":null,"source":"GHSA-mj5r-hh7j-4gxf"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2026.1.24-3"],"package":"clawdbot","purl":"pkg:npm/clawdbot","source":"GHSA-mj5r-hh7j-4gxf"},{"ecosystem":"npm","fixed":["2026.2.14"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":null,"source":"GHSA-mj5r-hh7j-4gxf"},{"ecosystem":"npm","fixed":["2026.2.14"],"introduced":["0"],"last_affected":[],"package":"openclaw","purl":"pkg:npm/openclaw","source":"GHSA-mj5r-hh7j-4gxf"}],"prev":{"headline":"OpenClaw \u003c 2026.2.15 - Cache Poisoning via Deprecated SHA-1 Hash in Sandbox Configuration","id":"CVE-2026-28479"},"products":["OpenClaw"],"published":"2026-03-05","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["OpenClaw"]},"summary":"Attackers can bypass Telegram allowlist restrictions by spoofing identities using recycled usernames, allowing unauthorized interaction with bots.","url":"https://insights.sbomify.com/CVE-2026-28480/"}