Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The ZeptoClaw crate (crates.io, versions before 0.7.6) has a webhook channel that trusts the sender and chat_id fields in the request body and checks the allowlist against them. Authentication is optional and disabled by default, so an attacker who can reach the POST /webhook endpoint can impersonate an allowlisted sender and pick arbitrary chat IDs. Upgrade to version 0.7.6 or later. Until then, configure an auth_token for the webhook channel.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.2 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0021, the 11th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:19 UTC First seen by agentprime
- 31 Oct 2026, 15:19 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-46q5-g3j9-wx5c
- OSV: GHSA-46q5-g3j9-wx5c
- github.com/qhkm/zeptoclaw/security/advisories/GHSA-46q5-g3j9-wx5c
- nvd.nist.gov/vuln/detail/CVE-2026-32231
- github.com/qhkm/zeptoclaw/pull/324
- github.com/qhkm/zeptoclaw/commit/bf004a20d3687a0c1a9e052ec79536e30d6de134
- github.com/qhkm/zeptoclaw
- github.com/qhkm/zeptoclaw/releases/tag/v0.7.6