CVE-2025-53520: EG4 12kPV · CWE-494
Affects EG4 12kPVSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EG4 Electronics EG4 12kPV | Affected
| Fixed in– |
AI-suggested
Organizations should immediately implement strict controls around firmware update processes for EG4 12kPV devices. This includes restricting update sources to trusted and verified channels, disabling remote or USB-based firmware updates where possible, and enforcing physical security to prevent unauthorized USB access. Network segmentation should isolate these devices from general IT networks to reduce exposure. Monitoring and logging of all firmware update activities should be enhanced to detect suspicious behavior. Until a vendor patch is available, organizations might consider implementing application-layer integrity verification by manually verifying firmware hashes against trusted values before installation. Engaging with EG4 Electronics for timelines on patch releases and applying updates promptly once available is critical. Additionally, organizations should review and harden access controls to the EG4 Monitoring Center and serial interfaces, including multi-factor authentication and strict user permissions. Incident response plans should be updated to address potential firmware compromise scenarios.
Description
The affected product allows firmware updates to be downloaded from EG4's website, transferred via USB dongles, or installed through EG4's Monitoring Center (remote, cloud-connected interface) or via a serial connection, and can install these files without integrity checks. The TTComp archive format used for the firmware is unencrypted and can be unpacked and altered without detection.