# CVE-2025-41713: WAGO: Vulnerability in hardware switch circuit

> An unauthenticated remote attacker can bypass network segmentation during device boot due to undefined switch state, requiring firmware updates for WAGO CC100 switches.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 15 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-4x6r-qc3x-j39x

## What is CVE-2025-41713?

CVE-2025-41713 is a medium-severity vulnerability in WAGO CC100 0751-9301, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

During a short time frame while the device is booting an unauthenticated remote attacker can send traffic to unauthorized networks due to the switch operating in an undefined state until a CPU-induced reset allows proper configuration.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2025-41713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41713 is a medium-severity vulnerability in WAGO CC100 0751-9301, published on 15 Sep 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-41713 in the wild and no public exploit code.

Affected product: WAGO CC100 0751-9301. 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-41713/ (Markdown: https://insights.sbomify.com/CVE-2025-41713/index.md)
```

## Sources

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

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