Summary
ZeptoClaw: Generic webhook channel trusts caller-supplied identity fields; allowlist is checked against untrusted payload data
Impact
- Vulnerability type:
- Authentication/authorization bypass (identity spoofing)
- IDOR-style routing/control issue via attacker-chosen
chat_id
- Affected deployments:
- Any deployment exposing the generic webhook endpoint without strict upstream authentication and identity binding.
- Security consequences:
- Forged inbound messages from spoofed trusted users.
- Bypass of allowlist intent by injecting allowlisted sender IDs in payload.
- Cross-chat/session contamination or hijacking by choosing arbitrary
chat_id. - Potential unauthorized downstream agent/tool actions triggered by malicious input.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
CVE-2026-32231 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.7.6); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-32231? CVE-2026-32231 is a high-severity missing authentication for critical function vulnerability in zeptoclaw (rust), affecting versions <= 0.7.5. It is fixed in 0.7.6. A critical operation is accessible without requiring any authentication.
- How severe is CVE-2026-32231? CVE-2026-32231 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of zeptoclaw are affected by CVE-2026-32231? zeptoclaw (rust) versions <= 0.7.5 is affected.
- Is there a fix for CVE-2026-32231? Yes. CVE-2026-32231 is fixed in 0.7.6. Upgrade to this version or later.
- Is CVE-2026-32231 exploitable, and should I be worried? Whether CVE-2026-32231 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-32231 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-32231? Upgrade
zeptoclawto 0.7.6 or later.