CVE-2026-43535
highpriority · track · 32OT risk · elevatedEPSS 0.004 · 33 %ileDEEUUSEPSS · scored 2026-10-23
OpenClaw before 2026.4.14 contains an authorization context reuse vulnerability in collect-mode queue batches that allows messages from different senders to inherit the final sender's authorization context. Attackers can exploit this by sending multiple queued messages to drain batches using a more privileged sender's context, causing earlier messages to execute with elevated permissions.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.9–8.1
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (5)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-1161OpenClaw: Mehrere SchwachstellenDeutsch2026-04-16csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um erweiterte Rechte zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren oder andere, nicht näher spezifizierte Angriffe durchzuführen.
- GHSA-jwrq-8g5x-5fhmOpenClaw: Collect-mode queue batches could reuse the last sender authorization context2026-04-17ghsa · osvUS
## Summary Collect-mode queue batches could reuse the last sender authorization context. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `< 2026.4.14` - Patched versions: `>= 2026.4.14` ## Impact Collect-mode queued messages from different senders could be drained as one batch using the final sender's authorization context, allowing earlier messages to inherit a more privileged context. ## Technical Details The fix splits collect-mode batches by sender authorization context before dispatch, preserving each message's own trust state. ## Fix The issue was fixed in #66024. The first stable tag containing the fix is `v2026.4.14`, and `openclaw@2026.4.14` includes the fix. ## Fix Commit(s) - `43d4be902755c970b3d15608679761877718da69` - PR: #66024 ## Release Process Note Users should upgrade to `openclaw` 2026.4.14 or newer. The latest npm release, `2026.4.14`, already includes the fix. ## Credits Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.
also known as (2)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (8)
External citations — patches, advisories, analysis.
- https://github.com/openclaw/openclaw/releasesPatchcnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2026-43535cnnvd
- https://github.com/openclaw/openclaw/commit/43d4be902755c970b3d15608679761877718da69enisa_euvd
- https://github.com/openclaw/openclaw/security/advisories/GHSA-jwrq-8g5x-5fhmenisa_euvd
- https://www.vulncheck.com/advisories/openclaw-authorization-context-reuse-in-collect-mode-queue-batchesenisa_euvd
- https://github.com/openclaw/openclaw/commit/43d4be902755c970b3d15608679761877718da69Patchnvd
- https://github.com/openclaw/openclaw/security/advisories/GHSA-jwrq-8g5x-5fhmVendor Advisorynvd
- https://www.vulncheck.com/advisories/openclaw-authorization-context-reuse-in-collect-mode-queue-batchesThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan