# CVE-2025-41670: Untrusted Search Path

> Local low-privileged users can escalate privileges by manipulating files in user-writable directories used by privileged services.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-7grg-5m65-97hj

## What is CVE-2025-41670?

CVE-2025-41670 is a high-severity vulnerability in Phoenix Contact AXC F 1152, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A local user with low privileges may be able to influence the behavior of a privileged system service by manipulating configuration or application-related files located in user-writable areas of the filesystem. The affected service processes data from locations that are not sufficiently protected against modification by low-privileged users. As the service runs with elevated privileges, successful exploitation may result in a local privilege escalation.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2025-41670 being exploited?

There is no known exploitation of CVE-2025-41670 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41670 is a high-severity vulnerability in Phoenix Contact AXC F 1152, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41670 in the wild and no public exploit code.

Affected product: Phoenix Contact AXC F 1152. 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-41670/ (Markdown: https://insights.sbomify.com/CVE-2025-41670/index.md)
```

## Sources

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

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