qhkm zeptoclaw up to 0.7.5 /webhook sender/chat_id missing authentication

Summaryinfo

A vulnerability identified as critical has been detected in qhkm zeptoclaw up to 0.7.5. This affects an unknown function of the file /webhook. The manipulation of the argument sender/chat_id leads to missing authentication. This vulnerability is referenced as CVE-2026-32231. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in qhkm zeptoclaw up to 0.7.5. It has been rated as critical. This issue affects some unknown functionality of the file /webhook. The manipulation of the argument sender/chat_id with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

ZeptoClaw is a personal AI assistant. Prior to 0.7.6, the generic webhook channel trusts caller-supplied identity fields (sender, chat_id) from the request body and applies authorization checks to those untrusted values. Because authentication is optional and defaults to disabled (auth_token: None), an attacker who can reach POST /webhook can spoof an allowlisted sender and choose arbitrary chat_id values, enabling high-risk message spoofing and potential IDOR-style session/chat routing abuse. This vulnerability is fixed in 0.7.6.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-32231 since 03/11/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

Upgrading to version 0.7.6 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch bf004a20d3687a0c1a9e052ec79536e30d6de134 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• qhkm

Name

• zeptoclaw

Version

• 0.7.0
• 0.7.1
• 0.7.2
• 0.7.3
• 0.7.4
• 0.7.5

License

• open-source

Website

• Product: https://github.com/qhkm/zeptoclaw/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion