# CVE-2025-41722: Sauter: Hard-coded Authentication Credentials

> An attacker can extract private keys from Sauter devices to bypass authentication and access SOAP messages.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-p5c4-4hc3-4fp5

## What is CVE-2025-41722?

CVE-2025-41722 is a high-severity vulnerability in Sauter EY-modulo 5 ecos 5 ecos504/505, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The wsc server uses a hard-coded certificate to check the authenticity of SOAP messages. An unauthenticated remote attacker can extract private keys from the Software of the affected devices.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-41722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41722 is a high-severity vulnerability in Sauter EY-modulo 5 ecos 5 ecos504/505, published on 22 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-41722 in the wild and no public exploit code.

Affected product: Sauter EY-modulo 5 ecos 5 ecos504/505. 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-41722/ (Markdown: https://insights.sbomify.com/CVE-2025-41722/index.md)
```

## Sources

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

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