# CVE-2026-118607: Alpine iLX-F511 diagapp Command Injection Vulnerability


- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-534x-8vf3-m22c

## What is CVE-2026-118607?

CVE-2026-118607 is a medium-severity vulnerability in Alpine iLX-F511, published on 28 Oct 2026. 

### Official description

Alpine iLX-F511 diagapp Command Injection Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Alpine iLX-F511 devices. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the diagapp component. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-28750.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-118607?


## How do I fix CVE-2026-118607?

No fix has been published for CVE-2026-118607 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118607 being exploited?

There is no known exploitation of CVE-2026-118607 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118607 and fix it if it is affected.

What it is: CVE-2026-118607 is a medium-severity vulnerability in Alpine iLX-F511, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118607 in the wild and no public exploit code.

Affected product: Alpine iLX-F511. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118607/ (Markdown: https://insights.sbomify.com/CVE-2026-118607/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118607
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118607
- OSV: https://osv.dev/vulnerability/CVE-2026-118607

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118607/
Summaries are generated and may contain mistakes; the official description above is the record.