Description
clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
Published: 2026-06-06
Score: 8.4 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a world‑reachable IPC endpoint in clash‑verge‑service‑ipc. An unprivileged user can access the endpoint and send crafted requests, which the service accepts and executes without proper permission checks. This allows the attacker to gain higher privileges on the same host, potentially compromising the entire system. The vulnerability stems from an incorrect permission configuration (CWE-732) that leaves the IPC socket accessible to all local users. Because the service runs with elevated privileges, exploitation directly elevates the attacker’s privilege level. This issue has a CVSS score of 8.4, indicating high severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting no well‑known exploits have been observed yet. Nevertheless, the local attack vector warrants immediate remediation as it could be abused in environments where untrusted users have filesystem or process access.

Affected Systems

The affected product is Clash Verge Rev’s clash‑verge‑service‑ipc before version 2.3.0. All releases prior to v2.3.0 include the world‑reachable IPC endpoint.

Risk and Exploitability

The CVSS score of 8.4 reflects a high risk scenario where a local attacker can elevate privileges. Because the vulnerability requires local access to the IPC endpoint, systems with strict user separation or who deny shell access to unprivileged users are less likely to be affected. Still, any environment where local users can reach the service socket is at risk. There is no publicly available exploit catalogued, but the potential for local privilege escalation remains significant.

Generated by OpenCVE AI on June 7, 2026 at 02:20 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Clash Verge Rev to version 2.3.0 or later to remove the world‑reachable IPC endpoint.
  • If an upgrade is not immediately possible, modify the IPC socket permissions so that it is accessible only by privileged users, for example by changing the socket file’s mode to 0700 or by running the service under a dedicated system user.
  • Reconfigure the service to bind the IPC endpoint to localhost only or to restrict access via firewall or access control lists, thereby reducing exposure to untrusted local users.

Generated by OpenCVE AI on June 7, 2026 at 02:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 08 Jun 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sun, 07 Jun 2026 11:30:00 +0000

Type Values Removed Values Added
First Time appeared Clash Verge Rev
Clash Verge Rev clash-verge-service-ipc
Vendors & Products Clash Verge Rev
Clash Verge Rev clash-verge-service-ipc

Sun, 07 Jun 2026 02:45:00 +0000

Type Values Removed Values Added
Title World-Readable IPC Endpoint Enables Local Privilege Escalation in Clash Verge Service

Sun, 07 Jun 2026 01:00:00 +0000

Type Values Removed Values Added
Description clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
Weaknesses CWE-732
References
Metrics cvssV3_1

{'score': 8.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Clash Verge Rev Clash-verge-service-ipc
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-06-08T13:15:47.853Z

Reserved: 2026-02-16T00:00:00.000Z

Link: CVE-2026-26422

cve-icon Vulnrichment

Updated: 2026-06-08T13:15:44.078Z

cve-icon NVD

Status : Deferred

Published: 2026-06-06T23:16:43.947

Modified: 2026-06-08T15:16:44.370

Link: CVE-2026-26422

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-07T11:15:23Z

Weaknesses
  • CWE-732

    Incorrect Permission Assignment for Critical Resource