Skip to main content
VulnerabilityPublished

CVE-2026-44103: Phoenix Contact CHARX SEC-3150 · Unrestricted File Upload

Affects Phoenix Contact CHARX SEC-3150Source CVE Database V5

0

Mentioned vulnerabilities

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.9.1 when convenient.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-07-30.

Patch
Available – fixed in 1.9.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade CHARX to 1.9.1.

Affected software

ProductAffectedFixed in
Phoenix ContactCHARX SEC-3150Affected
  • >=1.0.0 <1.9.1
Fixed in
  • 1.9.1
Phoenix ContactCHARX SEC-3100Affected
  • >=1.0.0 <1.9.1
Fixed in
  • 1.9.1
Phoenix ContactCHARX SEC-3050Affected
  • >=1.0.0 <1.9.1
Fixed in
  • 1.9.1
Phoenix ContactCHARX SEC-3000Affected
  • >=1.0.0 <1.9.1
Fixed in
  • 1.9.1

Description

An unauthenticated remote attacker can inject malicious firmware into the internal charging module because the JupiCore service transmits firmware updates without performing integrity or verification check. Successful exploitation may compromise the integrity of the affected device. This vulnerability could be used in chain with CVE-2026-44104.

References

Community reviews

Loading reviews…