CVE-2026-28479

Affected Packages / Versions

• npm package: openclaw
• Affected versions: <= 2026.2.14
• Fixed version (pre-set): 2026.2.15

Description

The sandbox identifier cache key for Docker/browser sandbox configuration used SHA-1 to hash normalized configuration payloads.

SHA-1 is deprecated for cryptographic use and has known collision weaknesses. In this code path, deterministic IDs are used to decide whether an existing sandbox container can be reused safely. A collision in this hash could let one configuration be interpreted as another under the same sandbox cache identity, increasing the risk of cache poisoning and unsafe sandbox state reuse.

The implementation now uses SHA-256 for these deterministic hashes to restore collision resistance for this security-relevant identifier path.

Fix Commit(s)

• 559c8d993

Release Process Note

patched_versions is pre-set to 2026.2.15 for the next release. After that release is published, mark this advisory ready for publication.

Thanks @kexinoh ( of Tencent zhuque Lab, by https://github.com/Tencent/AI-Infra-Guard) for reporting.

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

CVE-2026-28479 has a CVSS score of 5.4 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.15); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28479? CVE-2026-28479 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in openclaw (npm), affecting versions <= 2026.2.14. It is fixed in 2026.2.15. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
2. How severe is CVE-2026-28479? CVE-2026-28479 has a CVSS score of 5.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-28479? openclaw (npm) versions <= 2026.2.14 is affected.
4. Is there a fix for CVE-2026-28479? Yes. CVE-2026-28479 is fixed in 2026.2.15. Upgrade to this version or later.
5. Is CVE-2026-28479 exploitable, and should I be worried? Whether CVE-2026-28479 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-28479 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-28479? Upgrade openclaw to 2026.2.15 or later.