# CVE-2026-22613: Security feature bypass in Network M3

> Insecure firmware upgrade validation allows Man-in-the-middle attacks, potentially leading to code execution on Eaton Network M3 devices.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-fp59-gwjf-4gq6

## What is CVE-2026-22613?

CVE-2026-22613 is a medium-severity vulnerability in Eaton Network M3, published on 9 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The server identity check mechanism for firmware upgrade performed via command shell is insecurely implemented potentially allowing an attacker to perform a Man-in-the-middle attack. This security issue has been fixed in the latest firmware version of Eaton 

Network M3

 which is available on the Eaton download center.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-22613?


## How do I fix CVE-2026-22613?

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

## Is CVE-2026-22613 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22613 and fix it if it is affected.

What it is: CVE-2026-22613 is a medium-severity vulnerability in Eaton Network M3, published on 9 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22613 in the wild and no public exploit code.

Affected product: Eaton Network M3. 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-2026-22613/ (Markdown: https://insights.sbomify.com/CVE-2026-22613/index.md)
```

## Sources

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

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