# CVE-2025-41717: Config-Upload Code Injection

> Unauthenticated attackers can trick privileged users into uploading malicious configs, leading to root-level code execution on Phoenix Contact routers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-2448-826c-4v5m

## What is CVE-2025-41717?

CVE-2025-41717 is a high-severity code injection vulnerability in Phoenix Contact CLOUD CLIENT 1101T-TX/TX, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An unauthenticated remote attacker can trick a high privileged user into uploading a malicious payload via the config-upload endpoint, leading to code injection as root. This results in a total loss of confidentiality, availability and integrity due to improper control of code generation ('Code Injection’).

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-41717 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41717 is a high-severity code injection vulnerability in Phoenix Contact CLOUD CLIENT 1101T-TX/TX, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-41717 in the wild and no public exploit code.

Affected product: Phoenix Contact CLOUD CLIENT 1101T-TX/TX. 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-41717/ (Markdown: https://insights.sbomify.com/CVE-2025-41717/index.md)
```

## Sources

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

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