Skip to main content
VulnerabilityPublished

CVE-2026-22907: SICK TDC-X401GL · Incorrect Privilege Assignment

Affects SICK TDC-X401GLSource CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 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
SICK AGTDC-X401GLAffected
  • <1.4.0
Fixed in–

AI-suggested

  1. Monitor SICK AG’s official channels for patches addressing CVE-2026-22907 and apply them immediately upon release.
  2. Until patches are available, restrict network access to TDC-X401GL devices by implementing strict firewall rules and network segmentation to isolate these devices from untrusted networks.
  3. Enforce the principle of least privilege by reviewing and minimizing user and service account permissions on the affected devices.
  4. Implement robust authentication and access control mechanisms to prevent unauthorized privilege escalation.
  5. Continuously monitor device logs and network traffic for unusual access patterns or attempts to access the filesystem.
  6. Conduct regular security audits and vulnerability assessments on industrial control systems to identify and remediate similar privilege assignment issues.
  7. Train operational technology (OT) personnel on the risks associated with privilege escalation vulnerabilities and incident response procedures.
  8. Consider deploying intrusion detection/prevention systems tailored for industrial environments to detect exploitation attempts.

Description

An attacker may gain unauthorized access to the host filesystem, potentially allowing them to read and modify system data.

References

Community reviews

Loading reviews…