Summary
ZeptoClaw: Email Sender Spoofing to bypass Header-Only From Allowlist Validation
Impact
- Vulnerability type: sender identity spoofing risk due to header-based authorization.
- Affected deployments: those using email channel allowlists where upstream anti-spoof controls are weak, misconfigured, or bypassed.
- Security effect:
- Spoofed
Fromheaders may bypass logical sender allowlist. - Malicious content can enter trusted automation/agent flows as if sent by authorized identities.
- Spoofed
- Risk is reduced in environments with strict SPF/DKIM/DMARC enforcement and strong inbound mail hygiene, but not eliminated at application layer.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
GHSA-4CM8-XPFV-JV6F has a CVSS score of 6.5 (Medium). 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 GHSA-4CM8-XPFV-JV6F? GHSA-4CM8-XPFV-JV6F is a medium-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 GHSA-4CM8-XPFV-JV6F? GHSA-4CM8-XPFV-JV6F has a CVSS score of 6.5 (Medium). 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 GHSA-4CM8-XPFV-JV6F? zeptoclaw (rust) versions <= 0.7.5 is affected.
- Is there a fix for GHSA-4CM8-XPFV-JV6F? Yes. GHSA-4CM8-XPFV-JV6F is fixed in 0.7.6. Upgrade to this version or later.
- Is GHSA-4CM8-XPFV-JV6F exploitable, and should I be worried? Whether GHSA-4CM8-XPFV-JV6F 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 GHSA-4CM8-XPFV-JV6F 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 GHSA-4CM8-XPFV-JV6F? Upgrade
zeptoclawto 0.7.6 or later.