CVE-2025-59462VulnerabilityPublished 27 Oct 2025

CVE-2025-59462: SICK TLOC100-100 all Firmware versions · Uncaught Exception

Affects SICK TLOC100-100 all Firmware versionsSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SICK AG TLOC100-100 all Firmware versions	Affected *	Fixed in–

AI-suggested

1. Restrict network access to the UpdateService and the C++ CLI client interfaces by implementing strict firewall rules and network segmentation to limit exposure to trusted management networks only. 2. Monitor update processes and device logs for abnormal terminations or crashes of the UpdateService to detect potential exploitation attempts early. 3. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous behaviors related to file transfer tampering. 4. Coordinate with SICK AG for timely release and deployment of firmware patches addressing this vulnerability; prioritize patching in environments with high exposure. 5. Implement redundancy and failover mechanisms for critical devices to maintain operational continuity during update disruptions. 6. Conduct regular security assessments and penetration tests focusing on update mechanisms and CLI client security. 7. Educate operational technology (OT) staff about this vulnerability and safe update procedures to minimize accidental exposure. 8. Consider isolating update operations in controlled environments to reduce the risk of tampering during file transfers.

Description

An attacker who tampers with the C++ CLI client may crash the UpdateService during file transfers, disrupting updates and availability.

Impact

For European organizations, especially those in manufacturing, industrial automation, and logistics sectors relying on SICK AG TLOC100-100 devices, this vulnerability can cause significant operational disruptions. The denial of service caused by crashing the UpdateService can halt firmware updates, potentially leaving devices outdated and vulnerable to other threats. This disruption can affect production lines, safety systems, and monitoring processes, leading to financial losses and safety risks. Since the vulnerability does not affect confidentiality or integrity, data breaches are unlikely; however, availability loss can have cascading effects on industrial processes. The medium severity suggests moderate risk but with potential for impactful downtime. Organizations with large deployments of these devices or those in critical infrastructure sectors are particularly vulnerable. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once patches are released. The impact is amplified in countries with dense industrial activity and reliance on SICK AG products, where operational continuity is paramount.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 11:21 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats