https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-16T18:45:55.451626+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-26316 BREW-openclaw-cli-CVE-2026-26316 — OpenClaw BlueBubbles webhook auth bypass via loopback proxy trust 2026-10-16T18:45:55.504097+00:00

Affected: Homebrew: openclaw-cli

### Summary

In affected versions, the optional BlueBubbles iMessage channel plugin could accept webhook requests as authenticated based only on the TCP peer address being loopback (`127.0.0.1`, `::1`, `::ffff:127.0.0.1`) even when the configured webhook secret was missing or incorrect. This does not affect the default iMessage integration unless BlueBubbles is installed and enabled.

### Affected Packages / Versions

- npm: `openclaw` `< 2026.2.13` - npm: `@openclaw/bluebubbles` `< 2026.2.13`

### Details

If a deployment exposes the BlueBubbles webhook endpoint through a same-host reverse proxy (or an attacker can reach loopback via SSRF), an unauthenticated party may be able to inject inbound webhook events into the agent pipeline.

### Fix Commit(s)

- f836c385ffc746cb954e8ee409f99d079bfdcd2f - 743f4b28495cdeb0d5bf76f6ebf4af01f6a02e5a (defense-in-depth)

### Mitigations

- Set a non-empty BlueBubbles webhook password. - Avoid deployments where a public-facing reverse proxy forwards to a loopback-bound Gateway without strong upstream authentication.

Thanks @MegaManSec (https://joshua.hu) of [AISLE Research Team](https://aisle.com/) for reporting.

 https://cve.radiocsirt.org/vuln/cnvd-2026-13381 cnvd-2026-13381 2026-10-16T18:45:55.504167+00:00 cnvd-2026-13381 https://cve.radiocsirt.org/vuln/euvd-2026-268955 EUVD-2026-268955 2026-10-16T18:45:55.504185+00:00 EUVD-2026-268955 https://cve.radiocsirt.org/vuln/fkie_cve-2026-26316 fkie_cve-2026-26316 2026-10-16T18:45:55.504198+00:00

OpenClaw is a personal AI assistant. Prior to 2026.2.13, the optional BlueBubbles iMessage channel plugin could accept webhook requests as authenticated based only on the TCP peer address being loopback (`127.0.0.1`, `::1`, `::ffff:127.0.0.1`) even when the configured webhook secret was missing or incorrect. This does not affect the default iMessage integration unless BlueBubbles is installed and enabled. Version 2026.2.13 contains a patch. Other mitigations include setting a non-empty BlueBubbles webhook password and avoiding deployments where a public-facing reverse proxy forwards to a loopback-bound Gateway without strong upstream authentication.

 https://cve.radiocsirt.org/vuln/ghsa-pchc-86f6-8758 GHSA-pchc-86f6-8758 — OpenClaw BlueBubbles webhook auth bypass via loopback proxy trust 2026-10-16T18:45:55.504221+00:00

Affected: npm: openclaw, npm: @openclaw/bluebubbles

### Summary

In affected versions, the optional BlueBubbles iMessage channel plugin could accept webhook requests as authenticated based only on the TCP peer address being loopback (`127.0.0.1`, `::1`, `::ffff:127.0.0.1`) even when the configured webhook secret was missing or incorrect. This does not affect the default iMessage integration unless BlueBubbles is installed and enabled.

### Affected Packages / Versions

- npm: `openclaw` `< 2026.2.13` - npm: `@openclaw/bluebubbles` `< 2026.2.13`

### Details

If a deployment exposes the BlueBubbles webhook endpoint through a same-host reverse proxy (or an attacker can reach loopback via SSRF), an unauthenticated party may be able to inject inbound webhook events into the agent pipeline.

### Fix Commit(s)

- f836c385ffc746cb954e8ee409f99d079bfdcd2f - 743f4b28495cdeb0d5bf76f6ebf4af01f6a02e5a (defense-in-depth)

### Mitigations

- Set a non-empty BlueBubbles webhook password. - Avoid deployments where a public-facing reverse proxy forwards to a loopback-bound Gateway without strong upstream authentication.

Thanks @MegaManSec (https://joshua.hu) of [AISLE Research Team](https://aisle.com/) for reporting.