Skip to content
Fencer Intel
high 7.5

CVE-2026-41032 json

Phoenix Contact: Unauthenticated log download vulnerability in the firmware of CHARX SEC-3xxx charging controllers

published 5mo ago modified 3mo ago also EUVD-2026-34070

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

Summary

It is possible for an unauthenticated adjacent attacker to download log files of the controller, which may disclose some restricted information.

Patch / fix

  • Phoenix Contact CHARX SEC-3150 1.9.0
  • Phoenix Contact CHARX SEC-3100 1.9.0
  • Phoenix Contact CHARX SEC-3050 1.9.0
  • Phoenix Contact CHARX SEC-3000 1.9.0

Is CVE-2026-41032 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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

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

CVSS scores

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

Affected products

  • Phoenix Contact CHARX SEC-3150
  • Phoenix Contact CHARX SEC-3100
  • Phoenix Contact CHARX SEC-3050
  • Phoenix Contact CHARX SEC-3000

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.