# CVE-2025-9474: Mihomo Party Socket sysproxy.ts enableSysProxy temp file

> Local attackers can exploit insecure temporary file permissions in the system proxy handler to potentially escalate privileges or read sensitive data.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 5 Sep 2025
- **Also known as:** GHSA-f35p-mp22-6w3m

## What is CVE-2025-9474?

CVE-2025-9474 is a low-severity vulnerability in Mihomo Party, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in Mihomo Party up to 1.8.1 on macOS. Affected is the function enableSysProxy of the file src/main/sys/sysproxy.ts of the component Socket Handler. The manipulation results in creation of temporary file with insecure permissions. The attack requires a local approach. This attack is characterized by high complexity. The exploitability is told to be difficult. The exploit is now public and may be used.

Weakness: CWE-378 (Creation of Temporary File With Insecure Permissions), CWE-377 (DEPRECATED: Insecure Temporary File)

## Which versions are affected by CVE-2025-9474?


## How do I fix CVE-2025-9474?

No fix has been published for CVE-2025-9474 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9474 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9474 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9474 and fix it if it is affected.

What it is: CVE-2025-9474 is a low-severity vulnerability in Mihomo Party, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9474 exists.

Affected product: Mihomo Party. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9474/ (Markdown: https://insights.sbomify.com/CVE-2025-9474/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9474
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9474
- OSV: https://osv.dev/vulnerability/CVE-2025-9474

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9474/
Summaries are generated and may contain mistakes; the official description above is the record.