Skip to main content
CVE-2026-22542VulnerabilityPublished

CVE-2026-22542: EFACEC QC 60/90/120 · Uncontrolled Resource Consumption

Affects EFACEC QC 60/90/120Source CVE Database V5

0

Not known to be exploited · CVSS 9.2 Critical.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jan 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

Affected software

ProductAffectedFixed in
EFACECQC 60/90/120Affected
  • =8
Fixed in–

AI-suggested

1. Immediately restrict access to the internal network segments hosting EFACEC QC 60/90/120 devices, ensuring only trusted and authorized systems can communicate with them. 2. Disable the Telnet service on affected devices if possible, or replace it with more secure protocols like SSH. 3. Implement network-level controls such as firewalls and intrusion detection/prevention systems to monitor and block multiple concurrent Telnet connections from the same source. 4. Conduct regular network traffic analysis to detect unusual connection patterns indicative of exploitation attempts. 5. Engage with EFACEC support or vendors to obtain patches or firmware updates as soon as they become available. 6. Develop and test incident response plans specifically addressing denial of service scenarios affecting industrial control devices. 7. Segment industrial control networks from corporate IT networks to limit attacker movement and exposure. 8. Educate internal teams about the risks of this vulnerability and the importance of internal network security hygiene.

Description

An attacker with access to the system's internal network can cause a denial of service on the system by making two concurrent connections through the Telnet service.

References

Community reviews

Loading reviews…