Skip to main content
CVE-2025-59459VulnerabilityPublished Updated

CVE-2025-59459: SICK TLOC100-100 · Unthrottled Resource Allocation

Affects SICK TLOC100-100Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-26.

What to do

Affected software

ProductAffectedFixed in
SICK AG TLOC100-100Affected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2025-59459, organizations should implement strict SSH access controls, including the use of strong authentication methods such as key-based authentication and disabling password-based logins. Network segmentation should be enforced to restrict SSH access to trusted hosts only, minimizing the attack surface. Monitoring and alerting on unusual resource consumption or service disruptions on the TLOC100-100 devices can provide early warning of exploitation attempts. If possible, limit the number of unprivileged accounts with SSH access and regularly audit these accounts for necessity and activity. Employ rate limiting or connection throttling at the network level to reduce the risk of resource exhaustion attacks. Incident response plans should include procedures for recovery from device DoS conditions, including physical access if remote management is lost. Finally, maintain up-to-date inventories of affected devices to prioritize remediation efforts.

Description

An attacker that gains SSH access to an unprivileged account may be able to disrupt services (including SSH), causing persistent loss of availability.

References

Community reviews

Loading reviews…