Skip to main content
VulnerabilityPublished

CVE-2026-22544: EFACEC QC 60/90/120 · Cleartext Transmission

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

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% 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:H/VI:N/VA:N/SC:N/SI:N/SA:N

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 segment networks to isolate EFACEC QC 60/90/120 devices from general IT and internet-facing networks to limit attacker access.
  2. Employ encrypted VPN tunnels or IPsec to secure all communications to and from the affected devices until patches are available.
  3. Monitor network traffic for unencrypted credential transmissions and unusual access patterns using intrusion detection systems (IDS) and network traffic analysis tools.
  4. Restrict network access to the devices by implementing strict firewall rules and access control lists (ACLs) allowing only trusted management hosts.
  5. Coordinate with EFACEC for timely patch releases and apply updates as soon as they become available.
  6. Conduct regular credential audits and enforce strong password policies to reduce the impact of potential credential compromise.
  7. Train network and security teams to recognize signs of credential interception and lateral movement.
  8. Consider deploying network encryption gateways or proxies if native device encryption cannot be implemented immediately.

Description

An attacker with a network connection could detect credentials in clear text.

References

Community reviews

Loading reviews…