Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@openclaw/bluebubbles

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5npmAmendedPublished

    OpenClaw BlueBubbles webhook auth bypass via loopback proxy trust

    CVE-2026-26316 · GHSA-pchc-86f6-8758

    Affected
    • npm @openclaw/bluebubbles < 2026.2.13
    Fixed in
    2026.2.13· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 2026.2.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →