HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 82018 igel os 12 11 secure boot bypass via unsigned
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 6.8CVE-2026-82018

IGEL OS 12 / 11 Secure Boot Bypass via Unsigned igel.conf FileCVE-2026-82018

Answer in brief

CVE-2026-82018 records a Medium severity (CVSS 6.8) vulnerability in IGEL OS 12 / 11 Secure Boot Bypass via Unsigned igel.conf File. The current sources do not mark it as known exploited. The current feed maps IGEL/IGEL OS 11 (generic), IGEL/IGEL OS 11 (generic), IGEL/IGEL OS 12 (generic), IGEL/IGEL OS 12 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Oct 1, 2026Source checked Oct 13, 2026First seen by HOL Aug 28, 2026Material review Oct 1, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 6.8
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps IGEL/IGEL OS 11 (generic), IGEL/IGEL OS 11 (generic), IGEL/IGEL OS 12 (generic), IGEL/IGEL OS 12 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
IGEL/IGEL OS 11generic>=11.0.0 <11.11.15011.11.150
IGEL/IGEL OS 11generic*Not reported
IGEL/IGEL OS 12generic12.0.0Not reported
IGEL/IGEL OS 12generic>=12.0.0 <=12.8.2Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for IGEL/IGEL OS 11, IGEL/IGEL OS 11, IGEL/IGEL OS 12.
  2. 2Review the reported fix. Update IGEL/IGEL OS 11 to 11.11.150 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 28, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 1, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 28, 2026

Sources and claim methodology

  • Source referenceblog.amberwolf.com
  • Source referencekb.igel.com
  • Source referencemedia.defcon.org
  • Source referencevulncheck.com
Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Security Vulnerability identified in IBM TRIRIGA - Zip SlipSame generic ecosystem
  • Edimax BR-6208AC QoS Page formQoS cross site scriptingSame generic ecosystem
  • code-projects Online Ticket Reservation System medallion.sql file information disclosureSame generic ecosystem
  • code-projects Matrimonial System matrimony.sql file accessSame generic ecosystem
  • EricLBuehler mistral.rs media_source.rs is_global_ip server-side request forgerySame generic ecosystem
  • EricLBuehler Mistral.rs handlers.rs calibration_apply path traversalSame generic ecosystem

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-636
Source
CVE List V5
Source checked
Oct 13, 2026
References
4 linked sources
Open source record