CVE-2026-8305 is a high severity (7.3) improper authentication flaw in OpenClaw up to 2026.1.24, in the BlueBubbles webhook handler. The record says a public exploit exists. Upgrade to OpenClaw 2026.2.12 or later, which the record and the release notes name as the fix.
What's affected
The record lists OpenClaw up to 2026.1.24. It says upgrading to 2026.2.12 resolves the issue and names the patch commit a6653be. The affected function is handleBlueBubblesWebhookRequest in extensions/bluebubbles/src/monitor.ts.
The 2026.2.12 release notes list a fix titled "BlueBubbles: fix webhook auth bypass via loopback proxy trust", which matches. If you do not use the BlueBubbles extension, this path is not in use, but upgrading is still the safe choice.
How to check if you're exposed
Check the installed version.
npm ls -g 2>/dev/null | grep -i openclaw
If you run it from source or a container, read the version from the release tag or image tag. Then check whether the BlueBubbles extension is enabled and whether its webhook is reachable from outside, including through a reverse proxy.
What to do now
- Find every OpenClaw install and its version.
- Upgrade to 2026.2.12 or later, and read the release notes.
- If you use the BlueBubbles webhook, review your reverse proxy settings so the service does not trust traffic it should not.
- Rotate any secrets or tokens the webhook handles if you suspect misuse.
- Review webhook access logs for requests you do not recognize.
Why it matters
The weakness is CWE-287, improper authentication. According to the release note, the problem involved trust placed in a loopback proxy. When an application treats traffic as local because it arrives through a proxy on the same machine, a request from anywhere can look local.
The record says the exploit is public. It is not listed in CISA's KEV catalog, and I do not know whether it has been used. The score is 7.3 because the vector shows low impact on each of confidentiality, integrity and availability.
The detail that matters most in this record is the phrase about loopback proxy trust. Many self hosted tools sit behind a reverse proxy on the same machine, and many treat requests from the loopback address as already trusted. When a proxy forwards outside traffic from that address, the check no longer means what the code thinks it means.
That is a configuration pattern you can audit in your own services, beyond this one. For each service you run behind a proxy, ask what it does with the client address and with forwarded headers. If it grants extra trust to local traffic, make sure the proxy cannot make remote traffic look local.
The record says the exploit is public, which raises the urgency for any instance that exposes the BlueBubbles webhook. Upgrade to 2026.2.12 or later. If you cannot, disable the BlueBubbles extension until you can.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Does the loopback proxy detail mean I should check my reverse proxy?
Yes. Any setup that puts a proxy in front of a service on the same host deserves a check on what the service trusts.
Sources
Last reviewed: 19 October 2026.
