Futureweb

Security

Siemens Software Center loaded code from the wrong search path

Siemens says Software Center's search-path flaw was fixed in the October 15 release and that existing installs update on their own. CISA then catalogued active exploitation.

The short version

Siemens says it fixed the Software Center search-path flaw in the October 15 release and that existing installations update automatically. CISA added the flaw to the known-exploited catalog on October 20, 2026, after confirming active exploitation.

A loader search, then a catalog row

Siemens ProductCERT says it validated active exploitation of CVE-2026-110936, a library side-load in Software Center, and that the weakness was fixed in the October 15 release. Existing installations, Siemens says, update automatically. CISA's October 20 alert then put the same identifier on the known-exploited catalog, titled as an uncontrolled search path element. heise's October 21 story is the press account that bundled the Siemens row with Plex and SiteGuard. The order matters. The vendor fix is October 15. The public confirmation of in-the-wild use followed. An install that already took the automatic update is on the fixed release Siemens named. An install that did not is the product the catalog is talking about.What the KEV catalog adds.

What an uncontrolled search path is

The weakness class is the loader's search. A program asks for a library by a short name, and the operating system looks in a directory a caller can write, often beside the executable, before it looks in a directory only an administrator controls. A planted file with the expected name is what runs. CISA's title for the row is that class. Siemens' title is the side-load. This page does not name the library file, a download location, or a network indicator. Those belong in the vendor notice for the person confirming an install. The mechanism an operator needs is the class plus the release: October 15, automatic for existing installations.SiteGuard's shell is not a request.

The release is the package

A fix that arrives as an automatic update is only a fix on machines where that update ran. Siemens' sentence is that existing installations update on their own after the October 15 release. The catalog entry is the reason to check that the sentence came true on the machines you have, because exploitation was already validated. heise reported the warning. It did not ship the installer. A signature on the package, in the sense already filed on the software desk, is how you know the bits that arrived are the publisher's. An automatic channel that pulled the October 15 release is that check succeeding. A machine offline since before the release is the exception the catalog is for.A signature on a package.

The borrow checker does not steer the loader

Safe Rust rejects a use-after-free in the code it compiles. It does not tell Windows which directory to search when a binary asks for a library. A flawless borrow check and a planted library can be true on the same PC. Remade with Rust's claim, in the learn note, is a ground-up rebuild rather than a wrapper around the old program. That matters here only as a replacement: the shipped program is not Software Center, and it does not ask the loader to resolve a short library name from a folder next to the executable. The note is about memory safety first. The loader control is the separate decision not to search.Why Remade with Rust rebuilds the primitive.

A wrapper would keep the search

A Rust front end that still launches Software Center, or still loads the same helper libraries by short name, inherits the search path. The rebuild counts when the hot path is the new program. An unsafe block that calls LoadLibrary on a caller-influenced path would write the catalog row back in, in one line. Naming that block is the review rule. None of this uninstalls Software Center from an engineering workstation. The October 15 release does that job. The rebuild explains why a MATA service is not sitting in the same search, not why a Siemens customer can skip the update.What an unsafe block has to name.

Campaign writeups are not a second flaw

The security wire on October 21 also carried a report of a named group abusing a sandbox product's library load, and a report of a decades-old Windows utility used to coax a person into running a command. Those are adjacent classes: a loader search, and a person persuaded to execute. They are not CVE-2026-110936, and this page does not merge them into Siemens' release. The Chrome warning already filed is the control aimed at the pasted command. Siemens' October 15 release is the control aimed at Software Center. A reader who wants the sandbox campaign can read the outlet. The record kept here is the vendor fix plus the catalog row.The advisory is the story.

A MATA node runs the build you deployed

MATA's public model puts keys on the holder's device and runs memory-safe code without requiring an external server to hold the data. The property that answers a search-path flaw is where code comes from. The node runs the build that was deployed onto it. It does not resolve a short library name from a directory a downloaded installer can write. There is no Software Center process on that path whose loader will prefer a planted file. The digital-freedom note is the published statement that the stack was chosen so the code and the keys stay with the person. It is not a Siemens installer.How MATA keeps keys on the device.

The holder is not a search directory

The key stays with the holder. A verifier checks a signature from that key. Nothing in the handshake searches a folder beside an executable for extra code to trust. That is a different trust decision from Software Center's loader, which trusted the search order. Futureweb's key brief is the paired page: possession of the key is the credential, and a file dropped next to a program is not. Workstations that still run Software Center take the October 15 update Siemens described. The mesh does not push that installer, and it does not need to, because it does not run the program.The key stays with the holder.

Check the automatic update actually landed

Siemens' remedy is the October 15 release and the claim that existing installations update automatically. CISA's remedy is the catalog row that says exploitation has been observed, so the check is whether the automatic update reached the machine. heise is the October 21 account of the warning, useful as a second newsroom and not as a build list. A version string an operator reads off the installed Software Center is the fact that decides. The mesh's fact is simpler. The node is running the build you put there, and a library in a download folder is not part of that build.A patch window and the version.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Siemens ProductCERT
  2. CISA alert
  3. heise online

Questions

What is CVE-2026-110936?

CISA titles it an uncontrolled search path element in Siemens Software Center. Siemens says the weakness is a library side-load, that exploitation is active, and that the October 15 release is the fix.

Does the borrow checker stop a loader search?

No. Windows decides where it looks for a library. Safe Rust does not change that search. The control is a program that does not load a code library from a directory a caller can plant.

What should an existing install do?

Siemens says existing installations update automatically to the fixed release. CISA's catalog entry is the record that exploitation was already happening, so an install that did not take the automatic update is still the affected product.

How is a MATA node different from Software Center?

A MATA node runs the build that was deployed. It does not pick up a library because a downloaded installer found one beside the executable. Software Center, where you still use it, takes Siemens' update.

Is this the same warning as SiteGuard?

It is the same CISA alert and the same heise account, and it is a different product and a different weakness. SiteGuard's row is command injection. This row is where the loader searches.