LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22542: DENIAL OF SERVICE FOR CONCURRENT CONNECTIONS ON TELNET

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.

CriticalCVSS 9.2Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-22542 is a denial-of-service issue in EFACEC QC 60/90/120 version 8. A person already on the internal network can disrupt availability by opening two concurrent Telnet connections. The reported impact is high because it can affect system availability, but the public record does not show active exploitation or a named patch.

Executive priority

Prioritize this for environments using the affected EFACEC systems in critical operations. The issue can disrupt availability from the internal network with low complexity. Treat it as urgent for asset owners, but avoid assuming active exploitation or an available patch until vendor guidance is confirmed.

Technical view

The CVE describes CWE-400 resource consumption in the Telnet service of EFACEC QC 60/90/120 version 8. The CVSS 4.0 score is 9.2, with network attack vector, low complexity, no privileges, and high availability impact. The condition requires access to the internal network and concurrent Telnet connections.

Likely exposure

Exposure is most relevant where affected EFACEC QC 60/90/120 version 8 systems are reachable over Telnet from internal networks. Internet exposure is not stated in the source. Organizations without these models, this version, or enabled/reachable Telnet are less likely to be exposed.

Exploitation context

The source states an attacker with internal network access can cause denial of service using two concurrent Telnet connections. CISA KEV status is false in the provided data, and no cited source claims active exploitation. Public details are limited, so operational impact should be assessed in the specific deployment context.

Researcher notes

The public CVE data is sparse. Key missing items include vendor advisory details, patch status, exact affected build scope beyond version 8, and operational recovery behavior. Do not infer broader EFACEC product impact. Focus validation on Telnet reachability, version confirmation, and vendor communications.

Mitigation direction

  • Identify whether EFACEC QC 60/90/120 version 8 is deployed.
  • Check EFACEC or Thales guidance for updates or official mitigations.
  • Review whether Telnet is required for operations.
  • Restrict Telnet access to trusted management networks where feasible.
  • Monitor affected systems for unexpected Telnet connection activity.
  • Document compensating controls until vendor guidance is confirmed.

Validation and detection

  • Inventory EFACEC QC 60/90/120 assets and firmware versions.
  • Confirm whether Telnet is enabled and reachable internally.
  • Review network segmentation around affected systems.
  • Check logs for unusual concurrent Telnet sessions or availability events.
  • Verify any vendor-recommended update or configuration change was applied.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22542 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-22542Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EFACECQC 60/90/1208unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.