An unauthenticated vulnerability in the ZeptoClaw personal AI assistant allows remote attackers to spoof identity fields and hijack chat sessions due to missing authorization checks.

This flaw exists because the application trusts caller-supplied identity fields, such as sender and chat_id, within the webhook request body without proper verification. Because authentication is optional and can be disabled, an unauthenticated attacker can reach the POST /webhook endpoint to manipulate these values.

The ability to spoof senders and manipulate chat IDs poses a significant risk to data integrity and internal communications. An attacker could impersonate trusted users or intercept sensitive information by routing chat traffic to unauthorized sessions, potentially leading to unauthorized disclosure of private interactions. With a CVSS score of 8.2, this high-severity vulnerability warrants immediate attention to prevent malicious exploitation.

Immediate Action: Update the ZeptoClaw package to version 0.7.6 or later immediately to enforce proper authentication and identity validation.

Proactive Monitoring: Review web access logs for suspicious POST requests targeting the /webhook endpoint, particularly those containing irregular or unexpected identity fields.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to inspect and block requests to the /webhook endpoint that do not originate from known, trusted IP addresses or that lack valid authentication tokens.

Public Exploit Available: No

Given the high CVSS score and the existence of a proof-of-concept, organizations running ZeptoClaw must prioritize patching to version 0.7.6. Failure to update the software exposes the system to identity spoofing and unauthorized data access. Security teams should ensure the update is applied across all deployments to mitigate this critical authorization flaw effectively.