Skip to content
Fencer Intel
high 8.8

CVE-2025-41735 json

Possible arbitrary file upload

published 11mo ago modified 22d ago also EUVD-2025-197983

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

A low privileged remote attacker can upload any file to an arbitrary location due to missing file check resulting in remote code execution.

Patch / fix

  • METZ CONNECT Energy-Controlling EWIO2-M 2.2.0
  • METZ CONNECT Energy-Controlling EWIO2-M-BM 2.2.0
  • METZ CONNECT Ethernet-IO EWIO2-BM 2.2.0

Is CVE-2025-41735 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-25-322-05 updated cvss 8.8

METZ CONNECT EWIO2

  • METZ CONNECT Energy-Controlling Firmware <2.2.0 METZ CONNECT Ethernet-IO Firmware <2.2.0
    affected: vendor fix
  • METZ CONNECT Energy-Controlling Firmware 2.2.0 METZ CONNECT Ethernet-IO Firmware 2.2.0
    fixed

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
11mo ago

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • METZ CONNECT Energy-Controlling EWIO2-M
  • METZ CONNECT Energy-Controlling EWIO2-M-BM
  • METZ CONNECT Ethernet-IO EWIO2-BM

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.