IGEL OS 12 before 12.9.0, 12.8.3 LTS and IGEL OS 11 before 11.11.150 contain a secure boot bypass vulnerability in the GRUB boot stage that allows physically present attackers to gain unauthorized root access by placing an unsigned empty file named igel.conf on a partition. Attackers can exploit GRUB's fail-open signature verification behavior to drop into an interactive GRUB prompt, then boot the device's own kernel with additional command-line arguments to obtain a root shell with the disk unlocked while leaving TPM PCR values unaltered.
CVE-2026-82018
Score 6.1 from GitHub Security Advisory published 2026-08-29. a secondary CVSS source baseline 6.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(high)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (4)
Auto-updated Aug 28, 2026IGEL OS 12 / 11 Secure Boot Bypass via Unsigned igel.conf File | Advisories | VulnCheck
https://www.vulncheck.com/advisories/igel-os-12-11-secure-boot-bypass-via-unsigned-igel-conf-fileISN 2026-20: GRUB Shell Escape in IGEL OS | IGEL Knowledge Base
https://kb.igel.com/en/security-safety/current/isn-2026-20-grub-shell-escape-in-igel-osThin Client? Thin Crypto: An overview.
https://blog.amberwolf.com/blog/2026/august/thin-client-thin-crypto-overview/Vendor Advisories for CVE-2026-82018(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:37 UTCEG score recompute
- 2026-08-29 20:36 UTCGHSA enrichment
- 2026-08-28 22:38 UTCEG score recompute
- 2026-08-28 22:01 UTCEG score recompute
- 2026-08-28 21:59 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-82018?
When was CVE-2026-82018 disclosed?
Is CVE-2026-82018 actively exploited?
What is the CVSS score of CVE-2026-82018?
How do I remediate CVE-2026-82018?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82018
Is Your Infrastructure Affected by CVE-2026-82018?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.