Skip to content
IoT

CVE-2026-44100

8.8
High
EPSS 0.31%Patch availableJul 30, 2026

Unauthenticated remote reconfiguration of EV charging points

common questions

Is CVE-2026-44100 being exploited?

Not confirmed. CVE-2026-44100 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.

How severe is CVE-2026-44100?

CVE-2026-44100 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-44100?

Yes. A fix has been recorded for CVE-2026-44100. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-44100 affect?

CVE-2026-44100 affects CHARX JupiCore service, JupiCore-managed EV charging points/stations, JupiCore management interfaces. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-44100?

Isolate JupiCore, restrict network access, monitor logs, block internet access, apply vendor patch when available

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
CHARX JupiCore serviceJupiCore-managed EV charging points/stationsJupiCore management interfaces
impact

Remote unauthenticated attacker can reconfigure charging points to disclose UIDs, tamper files, and cause Denial-of-Service, disrupting charging and billing.

action required

Immediate action required

affected versions
Phoenix Contact CHARX SEC-3000
  • affected>= 1.0.0 and < 1.9.1
Phoenix Contact CHARX SEC-3050
  • affected>= 1.0.0 and < 1.9.1
Phoenix Contact CHARX SEC-3100
  • affected>= 1.0.0 and < 1.9.1
Phoenix Contact CHARX SEC-3150
  • affected>= 1.0.0 and < 1.9.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free