Skip to main content
VulnerabilityPublished Updated

CVE-2026-43579: OpenClaw · Nostr profile mutation routes allowed operator.write config persistence

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-43579· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 2026.4.10 when convenient.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.4.10
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.4.10.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.4.10
Fixed in
  • 2026.4.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade openclaw to version 2026.4.10 or later. The fix is included starting from 2026.4.10, with the latest npm release 2026.4.14 containing the patch. No additional mitigation is required once updated.

Description

A vulnerability in the Openclaw CLI Nostr plugin allowed profile mutation routes to persist profile configuration without requiring admin authority. This issue affects versions prior to 2026.4.10 and was fixed by enforcing the operator.admin scope for these routes. Users should upgrade to version 2026.4.10 or later to mitigate this vulnerability.

References

Community reviews

Loading reviews…