CVE-2026-32231Public exploitNetwork attack vector

Unauthenticated message spoofing via caller-controlled webhook identity

Published Mar 12, 2026 · Updated Mar 12, 2026

Authentication bypass in qhkm ZeptoClaw before 0.7.6 allows remote attackers to submit forged messages through the generic webhook. The validate_auth path accepts requests when auth_token is unset, then checks payload.sender against the allowlist and copies payload.sender and payload.chat_id into InboundMessage without binding either value to an authenticated identity. Reachability requires an enabled, network-accessible webhook without strict upstream authentication; accepted input can impersonate trusted senders and steer messages into attacker-selected chats or downstream agent actions.

CVSS severity8.2
High
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in qhkm ZeptoClaw before 0.7.6 allows remote attackers to submit forged messages through the generic webhook. The validate_auth path accepts requests when auth_token is unset, then checks payload.sender against the allowlist and copies payload.sender and payload.chat_id into InboundMessage without binding either value to an authenticated identity. Reachability requires an enabled, network-accessible webhook without strict upstream authentication; accepted input can impersonate trusted senders and steer messages into attacker-selected chats or downstream agent actions.

The record

CVE
CVE-2026-32231
Published
Mar 12, 2026
Updated
Mar 12, 2026
Vendor
qhkm
Product
ZeptoClaw
Classifications
CWE-345, CWE-306, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 12, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 12, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.7.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

qhkm · ZeptoClawversion=< 0.7.6

Published CVSS scores

8.2GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-345Insufficient Verification of Data Authenticity
CWE-306Missing Authentication for Critical Function
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo