# CVE-2026-96762: Kvcache-ai Mooncake authorization bypass in RPC segment handler

Source: https://junglewise.ai/threats/cve-2026-96762-a-vulnerability-was-determined-in-kvcache-ai-mooncake-up-to-0-3  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-24. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-96762 · Severity: high · CVSS 7.3 · Published 2026-09-24

Kvcache-ai Mooncake is a distributed storage system that manages memory segments across network nodes. An attacker who can reach the Master service can delete other clients' storage segments without authorization, causing data loss or service disruption. The vulnerability is a missing permission check in the segment unmounting function that allows cross-client deletion.

Technologies: [Kvcache-Ai Mooncake](https://junglewise.ai/threats/technologies/mooncake). Vendors: [Kvcache-Ai](https://junglewise.ai/threats/vendors/kvcache-ai).

## Quick answers

**Is CVE-2026-96762 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-96762 being exploited in the wild.

**How severe is CVE-2026-96762?** High severity, with a CVSS score of 7.3, published 24 September 2026.

**Which products and versions are affected?** Kvcache-Ai Mooncake up to 0.3.12 and 0.3.13.post1.

**Is there a fix for CVE-2026-96762?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-96762 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-96762?** Check whether you run Kvcache-Ai Mooncake at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The UnmountSegment RPC handler in MasterService fails to verify that the caller owns the supplied segment_id before processing deletion, allowing arbitrary segment destruction. The vulnerability is compounded by an unauthenticated HTTP endpoint (GET /get_segments_detail) on the admin interface that discloses all segment and client identifiers needed for exploitation. An attacker with network access to the RPC port (default 50051) and admin port (default 9003) can enumerate segments and delete any segment by manipulating the client_id and segment_id parameters.

## Affected products

- Kvcache-ai Mooncake up to 0.3.12 and 0.3.13.post1

## Timeline

- 2026-07-24: disclosed: Vulnerability confirmed in source code and dynamically reproduced
- 2026-09-24: advisory: Public disclosure via GitHub Gist

## References

- [https://gist.github.com/yyymk/76d099537af0e661dd01eacc82b9a7ea](https://gist.github.com/yyymk/76d099537af0e661dd01eacc82b9a7ea)
- [https://vuldb.com/cve/CVE-2026-96762](https://vuldb.com/cve/CVE-2026-96762)

## Related threats

- [Mooncake missing authentication in HTTP metadata server](https://junglewise.ai/threats/cve-2026-103765-mooncake-through-0-3-13-post1-contains-a-missing-authentication)
- [kvcache-ai mooncake denial of service in regex metadata queries](https://junglewise.ai/threats/cve-2026-96764-a-weakness-has-been-identified-in-kvcache-ai-mooncake-up-to-0-3)
- [kvcache-ai Mooncake access control bypass in MountSegment](https://junglewise.ai/threats/cve-2026-96763-a-security-flaw-has-been-discovered-in-kvcache-ai-mooncake-up-to)