Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-52268: n/a

0
High
VulnerabilityCVE-2025-52268cvecve-2025-52268
Published: Mon Oct 27 2025 (10/27/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2025-52268 is a vulnerability in the StarCharge Artemis AC Charger 7-22 kW v1. 0. 4 that involves a hardcoded AES encryption key. This flaw enables attackers to forge or decrypt valid login tokens, potentially allowing unauthorized access to the charger’s management interface. Exploitation does not require user interaction but does require knowledge of the hardcoded key, which is embedded in the device firmware. Although no known exploits are currently in the wild, the vulnerability poses a significant risk to the confidentiality and integrity of authentication tokens. European organizations deploying these chargers could face unauthorized control or manipulation of charging infrastructure. Mitigation requires firmware updates to remove hardcoded keys and implement secure key management. Countries with high EV adoption and infrastructure deployment, such as Germany, Netherlands, France, and the UK, are most likely to be affected. Given the potential for unauthorized access and control over critical charging infrastructure, the severity is assessed as high.

AI-Powered Analysis

AILast updated: 10/27/2025, 14:37:47 UTC

Technical Analysis

The vulnerability identified as CVE-2025-52268 affects the StarCharge Artemis AC Charger 7-22 kW version 1.0.4. The core issue is the presence of a hardcoded AES encryption key within the device’s firmware. This key is used to encrypt and decrypt login tokens that authenticate users to the charger’s management interface. Because the key is hardcoded and identical across devices, an attacker who obtains this key can forge valid login tokens or decrypt existing tokens, thereby bypassing authentication mechanisms. This allows unauthorized access to the charger’s administrative functions, potentially enabling attackers to manipulate charging sessions, disrupt service, or gain further network access if the charger is connected to broader infrastructure. The vulnerability does not require user interaction to exploit but does require knowledge or extraction of the hardcoded key, which could be obtained through firmware analysis or reverse engineering. No CVSS score has been assigned yet, and no public exploits are known at this time. However, the impact on confidentiality and integrity is significant, as authentication tokens can be compromised, undermining trust in the device’s security controls. The lack of patch links suggests that a fix may not yet be available, emphasizing the need for immediate risk assessment and mitigation by affected organizations.

Potential Impact

For European organizations, this vulnerability poses a critical risk to the security of electric vehicle (EV) charging infrastructure. Unauthorized access to charging stations could lead to service disruptions, unauthorized use or denial of charging services, and potential manipulation of billing or usage data. In a broader context, compromised chargers could serve as entry points into corporate or municipal networks, especially if integrated into smart grid or IoT environments. This could result in data breaches, operational disruptions, and reputational damage. Given the increasing reliance on EV infrastructure in Europe’s green energy transition, such vulnerabilities could undermine public trust and slow adoption. Additionally, attackers could leverage this access to cause physical damage or safety hazards by manipulating charging parameters. The impact on availability, while indirect, could be significant if attackers disable or degrade charging services in critical locations.

Mitigation Recommendations

Organizations should immediately inventory their EV charging infrastructure to identify any StarCharge Artemis AC Charger 7-22 kW devices running version 1.0.4. They should engage with the vendor to obtain firmware updates that remove the hardcoded AES key and implement secure key management practices, such as unique per-device keys or hardware security modules. Until patches are available, network segmentation should be enforced to isolate chargers from critical IT and OT networks. Access controls should be tightened, including monitoring and restricting administrative access to the chargers. Logging and anomaly detection should be enhanced to identify suspicious authentication attempts or token usage. If possible, replace affected devices with newer models that follow secure development practices. Additionally, organizations should conduct penetration testing and firmware analysis to verify that no other cryptographic weaknesses exist. Awareness training for operational staff on the risks of embedded device vulnerabilities is also recommended.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2025-06-16T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68ff8033ba6dffc5e2fca3ef

Added to database: 10/27/2025, 2:22:43 PM

Last enriched: 10/27/2025, 2:37:47 PM

Last updated: 10/27/2025, 4:47:07 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats