| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in SICK TDC-X401GL and classified as problematic. The affected element is an unknown function. This manipulation causes privileges assignment. This vulnerability is handled as CVE-2026-22916. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as problematic was found in SICK TDC-X401GL (the affected version unknown). Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a privileges assignment vulnerability. The CWE definition for the vulnerability is CWE-266. A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. As an impact it is known to affect availability. The summary by CVE is:
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.
This vulnerability is known as CVE-2026-22916 since 01/13/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/24/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔒
CNA Base Score: 4.3
CNA Vector (SICK AG): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Privileges assignmentCWE: CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/13/2026 CVE reserved01/15/2026 Advisory disclosed
01/15/2026 VulDB entry created
01/24/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2026-22916 (🔒)
GCVE (CVE): GCVE-0-2026-22916
GCVE (VulDB): GCVE-100-341281
Entry
Created: 01/15/2026 15:30Updated: 01/24/2026 13:11
Changes: 01/15/2026 15:30 (58), 01/24/2026 13:11 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.