dbcve.org
Tdc X401gl FirmwareOperating system · Sick

CVE-2026-22907

CRITICAL · 9.1 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 1.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability allows unauthorized access to the host filesystem, potentially enabling attackers to read and modify system data. The CVSS 9.1 score indicates a critical severity flaw, likely involving improper path validation, container isolation bypass, or insecure file handling that permits traversal outside intended boundaries.

MitigationImplement strict filesystem access controls, validate and sanitize all file path inputs, ensure proper container isolation if applicable, and restrict file system permissions to the minimum required for application functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tdc X401gl FirmwareOperating system
Affected:< 1.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Sick Tdc X401gl
    Identify the exact model number of the Sick device in your environment through device inventory, network discovery, or physical device labeling
    Affected if The device model is not Sick Tdc X401gl
  2. Check installed firmware version
    Access the device management interface or use vendor-specific commands to retrieve the current firmware version, then compare against the affected range of < 1.4.0
    Affected if Firmware version is 1.3.x or earlier, or cannot be determined but is reported as below 1.4.0
  3. Identify exposed filesystem interfaces
    Review network-exposed services, APIs, or management interfaces on the device that handle file operations such as file upload, download, configuration import/export, or logging
    Affected if Filesystem-related services or APIs are accessible over the network without additional authentication barriers
  4. Check configuration for path traversal settings
    Examine device configuration files or settings related to file handling, storage paths, and access control rules for any misconfigurations that allow unrestricted path traversal
    Affected if Configuration permits unrestricted file path manipulation or allows access outside intended directories
  5. Verify access control on file operations
    Test or inspect whether the device enforces proper authorization checks on file read/write operations, particularly through web interfaces or APIs
    Affected if File operations execute without proper authorization validation or allow access to system directories outside the application sandbox

You are affected if the device is a Sick Tdc X401gl running firmware version prior to 1.4.0 and has filesystem interfaces or file operation features exposed and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.0 or later
Fixed in 1.4.0
Interim mitigation

Implement strict filesystem access controls, validate and sanitize all file path inputs, ensure proper container isolation if applicable, and restrict file system permissions to the minimum required for application functionality.

Recommended fix Moderate confidence

Tdc X401gl Firmware version 1.4.0 or later

  1. 1. Obtain the official firmware version 1.4.0 or later for Tdc X401gl from the SICK website or authorized distributor
  2. 2. Review the SICK firmware upgrade documentation specific to the Tdc X401gl device
  3. 3. Create a backup of the current device configuration if the device supports configuration export
  4. 4. Follow the vendor's recommended firmware update procedure (typically via web interface, management console, or dedicated update tool)
  5. 5. Verify the firmware upgrade was successful by confirming the installed firmware version displays 1.4.0 or later
  6. 6. Test that the device is functioning normally and that unauthorized filesystem access is no longer possible
Caveat Review SICK release notes for any configuration changes or migration requirements between your current version and 1.4.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tdc X401gl Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22907 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data