<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T16:22:52.623613+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-27007</id>
    <title>CVE-2026-27007 — OpenClaw's sandbox config hash sorted primitive arrays and suppressed needed container recreation</title>
    <updated>2026-10-03T16:22:52.625974+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openclaw</p>
<p>OpenClaw is a personal AI assistant. Prior to version 2026.2.15, `normalizeForHash` in `src/agents/sandbox/config-hash.ts` recursively sorted arrays that contained only primitive values. This made order-sensitive sandbox configuration arrays hash to the same value even when order changed. In OpenClaw sandbox flows, this hash is used to decide whether existing sandbox containers should be recreated. As a result, order-only config changes (for example Docker `dns` and `binds` array order) could be treated as unchanged and stale containers could be reused. This is a configuration integrity issue affecting sandbox recreation behavior. Starting in version 2026.2.15, array ordering is preserved during hash normalization; only object key ordering remains normalized for deterministic hashing.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-27007"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xxvh-5hwj-42pp</id>
    <title>GHSA-xxvh-5hwj-42pp — OpenClaw's sandbox config hash sorted primitive arrays and suppressed needed container recreation</title>
    <updated>2026-10-03T16:22:52.626035+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Description</p>
<p>`normalizeForHash` in `src/agents/sandbox/config-hash.ts` recursively sorted arrays that contained only primitive values. This made order-sensitive sandbox configuration arrays hash to the same value even when order changed.</p>
<p>In OpenClaw sandbox flows, this hash is used to decide whether existing sandbox containers should be recreated. As a result, order-only config changes (for example Docker `dns` and `binds` array order) could be treated as unchanged and stale containers could be reused.</p>
<p>This is a configuration integrity issue affecting sandbox recreation behavior.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected: `&lt;=2026.2.14`
- Patched (planned next release): `&gt;=2026.2.15`
- Latest published npm version at triage time (2026-02-16): `2026.2.14`</p>
<p>## Remediation</p>
<p>Array ordering is now preserved during hash normalization; only object key ordering remains normalized for deterministic hashing.</p>
<p>## Fix Commit(s)</p>
<p>- `41ded303b4f6dae5afa854531ff837c3276ad60b`</p>
<p>## Release Process Note</p>
<p>`patched_versions` is pre-set to the planned next release (`2026.2.15`) so after npm publish, the advisory can be published directly without reopening version metadata edits.</p>
<p>Thanks @kexinoh ( of Tencent zhuque Lab, by https://github.com/Tencent/AI-Infra-Guard) for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xxvh-5hwj-42pp"/>
  </entry>
</feed>
