dbcve.org
Tdc X401gl FirmwareOperating system · Sick

CVE-2026-22916

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 with low privileges may be able to trigger critical system functions such as reboot or factory reset without proper restrictions, potentially leading to service disruption or loss of configuration.

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 is an authorization bypass vulnerability where low-privileged authenticated users can trigger critical system functions (reboot, factory reset) that should require higher privilege levels. The application likely lacks proper access control checks on administrative endpoints, allowing privilege escalation to privileged operations.

MitigationImplement role-based access control (RBAC) with explicit authorization verification before executing any critical system functions. Ensure all administrative endpoints validate user privilege levels and reject requests from unauthorized roles.

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:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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. Identify the device model and firmware version
    Access the device web interface or use the command-line interface (e.g., via SSH or serial console) and retrieve the system information or firmware version. Common commands include 'show version', 'system info', or checking the About/Status page in the web UI.
    Affected if The device is a Sick Tdc X401gl and is running any firmware version.
  2. Verify user role configuration
    Access the user management or administration settings in the device web interface or configuration files. Identify the roles assigned to different users and check if there is a distinction between low-privileged and privileged (administrator) roles.
    Affected if The system allows creating or assigning low-privileged user accounts without proper role separation from administrative functions.
  3. Inspect administrative endpoint access controls
    Review the API endpoints or web URLs used for critical functions such as reboot, factory reset, or system configuration. Check if these endpoints enforce role-based authorization by examining the application's authentication logic, configuration files, or API documentation.
    Affected if Administrative endpoints (for reboot, factory reset, etc.) do not verify that the requesting user has elevated privileges before executing the action.
  4. Check for missing authorization enforcement in critical functions
    If you have access to both a low-privileged and a privileged account, attempt to access or trigger critical system functions (reboot, factory reset, configuration changes) using the low-privileged account. Observe whether the request is rejected or allowed.
    Affected if Low-privileged authenticated users can successfully trigger critical system functions that should require administrator-level privileges.

Your environment is affected if you are using a Sick Tdc X401gl device with any firmware version where low-privileged users can access administrative endpoints for critical functions without proper authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement role-based access control (RBAC) with explicit authorization verification before executing any critical system functions. Ensure all administrative endpoints validate user privilege levels and reject requests from unauthorized roles.

Fix this in Tdc X401gl Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22916 — 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-22916 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