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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Product is meta-iot2050 at version V01.03.01 or later (all versions >= V01.03.01). The flaw is in the firmware update tool, which takes parts from a configuration file and runs them unchecked.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
Read the original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 7.3, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Product is meta-iot2050 at version V01.03.01 or later (all versions >= V01.03.01). The flaw is in the firmware update tool, which takes parts from a configuration file and runs them unchecked.Workaround: 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.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Siemens meta-iot2050
From V01.03.01
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-109830
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: cve.now feed data
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: cert-portal.siemens.com
Which versions are affected by CVE-2026-109830?
meta-iot2050: from V01.03.01.Source: cve.now feed data
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: cert-portal.siemens.com
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: cert-portal.siemens.com
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: cert-portal.siemens.com