CVE-2025-40751
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to simatic rtls locating manager 3.3 or later upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
A vulnerability has been identified in SIMATIC RTLS Locating Manager (All versions < V3.3). Affected SIMATIC RTLS Locating Manager Report Clients do not properly protect credentials that are used to authenticate to the server. This could allow an authenticated local attacker to extract the credentials and use them to escalate their access rights from the Manager to the Systemadministrator role.
- weakness
- CWE-522: Insufficiently Protected Credentials
- affected
- Siemens SIMATIC RTLS Locating Manager
- published ranges
- siemens simatic rtls locating manager < 3.3
- first unaffected version, by branch
- simatic rtls locating manager 3.3
- severity
- 6.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
- assigned by
- siemens
- published
- 2025-08-12
check us cert-portal.siemens.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 12 Aug 2025 | 0.00013 | |
| 13 Aug 2025 | 0.00012 | |
| 18 Aug 2025 | 0.00013 | |
| 13 Sep 2025 | 0.00015 | |
| 19 Oct 2025 | 0.00017 | |
| 12 Dec 2025 | 0.00022 | |
| 8 Jan 2026 | 0.00014 | |
| 20 Jan 2026 | 0.00015 | |
| 8 Mar 2026 | 0.00017 | |
| 28 Apr 2026 | 0.00021 | |
| 8 May 2026 | 0.00022 | |
| 8 Jun 2026 | 0.00059 | |
| 15 Jun 2026 | 0.00107 | scoring model v2026.06.15 |
| 13 Jul 2026 | 0.00115 | |
| 1 Sep 2026 | 0.00118 |
15 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-01 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: simatic rtls locating manager 3.3. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-40751', '2026-10-31T23:59:59.999999Z', now());