# CVE-2026-82017: IGEL OS 12 / 11 Boot Registry Parameter Injection via Unsigned Configuration Area

> Attackers with physical access can inject malicious kernel parameters via an unsigned configuration area, bypassing TPM measurements to execute code with boot privileges.

- **Severity:** High 8.6 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-jh8x-f5g5-w4rq

## What is CVE-2026-82017?

CVE-2026-82017 is a high-severity vulnerability in IGEL OS 11, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IGEL OS 12 before 12.7.6 and IGEL OS 11 before 11.11.150 contain a boot registry parameter injection vulnerability that allows attackers with physical access to execute arbitrary Linux loader parameters by writing to an unencrypted and unsigned configuration area read by the signed bootloader. Attackers can inject malicious kernel command line parameters that execute with boot environment privileges without triggering TPM PCR measurement failures, as the attack does not modify the measured boot code.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-82017 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82017 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82017 is a high-severity vulnerability in IGEL OS 11, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82017 exists.

Affected product: IGEL OS 11. 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-82017/ (Markdown: https://insights.sbomify.com/CVE-2026-82017/index.md)
```

## Sources

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

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