<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T13:44:37.493643+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28450</id>
    <title>BREW-openclaw-cli-CVE-2026-28450 — OpenClaw's unauthenticated Nostr profile HTTP endpoints allow remote profile/config tampering</title>
    <updated>2026-09-30T13:44:37.495101+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Summary
The OpenClaw Nostr channel plugin (optional, disabled by default, installed separately) exposes profile management HTTP endpoints under `/api/channels/nostr/:accountId/profile` (GET/PUT) and `/api/channels/nostr/:accountId/profile/import` (POST). In affected versions, these routes were dispatched via the gateway plugin HTTP layer without requiring gateway authentication, allowing unauthenticated remote callers to read or mutate the Nostr profile and persist changes to the gateway config. Profile updates are also published as a signed Nostr kind:0 event using the bot's private key.</p>
<p>Deployments that do not have the Nostr plugin installed and enabled are not impacted.</p>
<p>## Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected versions: `&lt;= 2026.2.9`
- Fixed versions: `&gt;= 2026.2.12`
- Scope note: only affects deployments with the optional `@openclaw/nostr` plugin installed and enabled</p>
<p>## Details
This is exploitable when the gateway HTTP port is reachable beyond localhost (for example: bound to `0.0.0.0`, exposed on a LAN, behind a reverse proxy, or via Tailscale Funnel/Serve).</p>
<p>Unauthenticated callers could update the Nostr profile and persist the new profile in the gateway config.</p>
<p>## Mitigation
Upgrade to `openclaw` `2026.2.12` or later.</p>
<p>As a temporary mitigation, restrict gateway HTTP exposure (bind loopback-only and/or enforce network-layer access controls) until upgraded.</p>
<p>## Fix
Gateway now requires gateway authentication for plugin HTTP requests…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28450"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-28450</id>
    <title>CVE-2026-28450 — OpenClaw &lt; 2026.2.12 - Unauthenticated Profile Tampering via Nostr Plugin HTTP Endpoints</title>
    <updated>2026-09-30T13:44:37.495294+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>OpenClaw versions prior to 2026.2.12 with the optional Nostr plugin enabled expose unauthenticated HTTP endpoints at /api/channels/nostr/:accountId/profile and /api/channels/nostr/:accountId/profile/import that allow reading and modifying Nostr profiles without gateway authentication. Remote attackers can exploit these endpoints to read sensitive profile data, modify Nostr profiles, persist malicious changes to gateway configuration, and publish signed Nostr events using the bot's private key when the gateway HTTP port is accessible beyond localhost.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-28450"/>
  </entry>
</feed>
