VORANT. Threat Intelligence Research Sign in Create a free account

Siemens SIMATIC RTLS Locating Manager arbitrary code execution

routine vulnerability manufacturing

Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.

Improper input validation in SIMATIC RTLS Locating Manager before V3.2 allows authenticated attackers to execute arbitrary code as SYSTEM.

Siemens SIMATIC RTLS Locating Manager versions prior to V3.2 contain an improper input validation vulnerability (CWE-20) in a backup script function. An authenticated remote attacker with high privileges within the application can exploit this to execute arbitrary code with NT Authority/SYSTEM privileges, gaining complete system control.

The vulnerability is assigned CVE-2025-40746 with a CVSS v3.1 score of 9.1 and CVSS v4 score of 9.4, reflecting its remotely exploitable nature and low attack complexity. The affected product is deployed worldwide in critical manufacturing environments. Siemens reports no known public exploitation at the time of advisory publication.

Mitigation requires immediate upgrade to SIMATIC RTLS Locating Manager V3.2 or later. Organizations should implement network segmentation, restrict administrative access, and ensure devices are not exposed to the internet. Remote access should be protected via VPN or equivalent secure channels.

Mentioned in this report

Vulnerabilities CVE-2025-40746

Detection guidance

SIMATIC RTLS Locating Manager Process Spawning Shell as SYSTEM

ATT&CK T1059.001

Detects PowerShell or cmd spawned as SYSTEM by a process running from an RTLS / Locating Manager install path, consistent with CVE-2025-40746 backup-script code execution. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: SIMATIC RTLS Locating Manager Process Spawning Shell as SYSTEM
description: Detects PowerShell, pwsh or cmd.exe running as NT AUTHORITY\SYSTEM with
  a parent process executing from an RTLS / Locating Manager path. Based on CVE-2025-40746,
  where improper input validation in the backup script function gives an authenticated
  high-privilege user SYSTEM code execution. The product path match is inferred from
  the product name, so tune it to the local install directory.
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-13
tags:
- attack.initial-access
- attack.t1190
- attack.execution
- attack.t1059.001
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|contains:
    - RTLS
    - Locating Manager
  selection_child:
    Image|endswith:
    - \powershell.exe
    - \pwsh.exe
    - \cmd.exe
    User|contains:
    - AUTHORITY
    - SYSTEM
  filter_backup_noise:
    CommandLine|contains: -Version
  condition: selection_parent and selection_child and not filter_backup_noise
falsepositives:
- Legitimate RTLS Locating Manager scheduled backup scripts that are launched through
  cmd.exe or PowerShell
- Administrators running maintenance scripts from the application directory
level: medium
id: 77c3e914-e9bc-58b1-bb37-7b25988ea95a
status: experimental
author: Vorant

Behavioural rules are generated from public reporting — validate in your environment before deploying.

Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-13

What this brief leaves out

This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.

It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.

A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.

Create a free account   What it costs