META-IOT2050 · CVE-2026-109830 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Siemens SSA-724261: the firmware update tool in meta-iot2050 (SIMATIC IOT2050 image layer) from V01.03.01 on passes parts of a configuration file to commands without checking them, so someone who can modify that file gets arbitrary commands run as root. CVSS is local, low privileges, user interaction required (7.3 v3.1 / 7.0 v4.0). Siemens says no fix is available; the fix is in the master branch and will ship in the next release. No exploitation or PoC reported.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Devices running a meta-iot2050 image (the Debian-based software layer for SIMATIC IOT2050) from V01.03.01 on, all versions, per Siemens. The attacker must be able to change a configuration file used by the firmware update tool and a user has to trigger it; commands then run as root. Systems where only trusted admins can touch that file are at much lower risk.
Not affected if config-file-not-writable-by-attacker
Who cares command-injection, embedded-linux, industrial-iot, local, meta-iot2050, no-fix, siemens, simatic-iot2050
A vulnerability has been identified in meta-iot2050 (All versions >= V01.03.01). Affected devices take parts from a configuration file and execute them unchecked. This could allow an attacker which is able to manipulate the configuration file to make the user execute arbitrary code on the device.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.