# CVE-2026-118602: Alpine iLX-F511 Fiv.System Exposed Dangerous Method Local Privilege Escalation Vulnerability


- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/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-cgg4-3hc7-7cqc

## What is CVE-2026-118602?

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

### Official description

Alpine iLX-F511 Fiv.System Exposed Dangerous Method Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Alpine iLX-F511. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

The specific flaw exists within the Fiv service. The issue results from an exposed dangerous method. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of root. Was ZDI-CAN-29095.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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


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

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

## Is CVE-2026-118602 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118602 is a high-severity vulnerability in Alpine iLX-F511, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118602 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-118602/ (Markdown: https://insights.sbomify.com/CVE-2026-118602/index.md)
```

## Sources

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

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