# CVE-2025-41706: Phoenix Contact: Webserver Denial of Service through Malformed Content-Length

> An unauthenticated remote attacker can cause a denial of service on Phoenix Contact industrial UPS devices by sending a malformed GET request with an over-long content-length.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-hvfm-qx34-wp84

## What is CVE-2025-41706?

CVE-2025-41706 is a medium-severity denial of service vulnerability in Phoenix Contact QUINT4-UPS/24DC/24DC/10/EIP, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The webserver is vulnerable to a denial of service condition. An unauthenticated remote attacker can craft a special GET request with an over-long content-length to trigger the issue without affecting the core functionality.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2025-41706 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41706 is a medium-severity denial of service vulnerability in Phoenix Contact QUINT4-UPS/24DC/24DC/10/EIP, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41706 in the wild and no public exploit code.

Affected product: Phoenix Contact QUINT4-UPS/24DC/24DC/10/EIP. 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-41706/ (Markdown: https://insights.sbomify.com/CVE-2025-41706/index.md)
```

## Sources

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

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