| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in SICK TDC-X401GL. This vulnerability affects unknown code. Such manipulation leads to information expsure. This vulnerability is referenced as CVE-2026-22915. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in SICK TDC-X401GL (affected version unknown). Affected by this issue is an unknown functionality. The manipulation with an unknown input leads to a information expsure vulnerability. Using CWE to declare the problem leads to CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. Impacted is confidentiality. CVE summarizes:
An attacker with low privileges may be able to read files from specific directories on the device, potentially exposing sensitive information.
This vulnerability is handled as CVE-2026-22915 since 01/13/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Information expsureCWE: CWE-497
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-22915 (🔒)
GCVE (CVE): GCVE-0-2026-22915
GCVE (VulDB): GCVE-100-341300
Entry
Created: 01/15/2026 15:37Updated: 01/24/2026 13:11
Changes: 01/15/2026 15:37 (58), 01/24/2026 13:11 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.