CVE-2026-110936
The record is as the index held it on 2026-10-18. The KEV listing and the EPSS score were read on 2026-10-21. The score is dated to the day it became true. The KEV state is dated to that read. Changes between those two dates are not all shown.
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
A vulnerability has been identified in Siemens Software Center (All versions < V4.0.9.8)
rank 65 = 40 + 17 + 0 + 0 + 8
rank@v1 · this cycle
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.00262 · CISA KEV listed · without this subject the record ranks 25
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 6.7, from NVD · without this subject the record ranks 48
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 65
How much of the world it touches
NVD CPE configurations
0 products in the CPE ranges · without this subject the record ranks 65
Someone else already set the date
CISA KEV remediation due date
CISA remediation date held · without this subject the record ranks 57
Hindsight · the state
Foresight · where to check next
This record is one instance of CWE-427, uncontrolled search path element. The index holds 1243 prior instances of this class, 2 KEV-listed. taxonomy@v1
Running Siemens Software Center? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Check your stack in the mirror · True as of 21 Oct 2026
Set up a watchlist (free with an account: one stack of three products)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.
Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Show full BOD 26-04 deadline
CISA scored it on 15 Oct 2026: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table
Exploit Status & Known PoCs a ladder, not a score
Current rung: Exploited in the wild · CISA KEV listed, 2026-10-20.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published
- RUNG 3Exploited in the wild · CISA KEV listed2026-10-20receipt
- RUNG 4Ransomware campaign use known
Affected & Fixed Versions as published
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
$13,100 = $4.99M incident cost x 1 exposure x 0.00262 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
Attack path
What it is stated by the CNA
A vulnerability has been identified in Siemens Software Center (All versions < V4.0.9.8). The affected application loads dynamic-link libraries (DLLs) from an uncontrolled search path. This could allow an authenticated local attacker to place a specially crafted DLL in a directory that the application searches, leading to arbitrary code execution with the privileges of the affected application. receipt
NVD's analysis a second authority
- severity
- 6.7 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- weakness
- CWE-427
- also scored by
- productcert@siemens.com 8.4 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
check it yourself cert-portal.siemens.com receipt
Dated events
Movement the material steps
Show all 2 observations
2 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The pattern, elsewhere
This record is one instance of CWE-427, uncontrolled search path element. The index holds 1243 prior instances of this class, 2 KEV-listed. cwe-consequences@4.20
1243 records in this class held. The six above are ranked by exploit maturity, then recency.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2026-110936.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.