---
id: "CVE-2025-47827"
kind: "vulnerability"
aliases: ["CVE-2025-47827"]
title: "In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a\u2026"
severity: "high"
cvss: 4.6
epss: null
exploited: true
status: "open"
category: "infrastructure"
products: [{"name": "IGEL IGEL OS", "fixed": [], "affected": "", "ecosystem": "vendor"}, {"name": "igel os", "fixed": ["11.01.100"], "affected": "< 11.01.100", "ecosystem": "vendor"}, {"name": "microsoft windows 10 1507", "fixed": ["10.0.10240.21161"], "affected": "< 10.0.10240.21161", "ecosystem": "vendor"}, {"name": "microsoft windows 10 1607", "fixed": ["10.0.14393.8519"], "affected": "< 10.0.14393.8519", "ecosystem": "vendor"}, {"name": "microsoft windows 10 1809", "fixed": ["10.0.17763.7919"], "affected": "< 10.0.17763.7919", "ecosystem": "vendor"}, {"name": "microsoft windows 10 21h2", "fixed": ["10.0.19044.6456"], "affected": "< 10.0.19044.6456", "ecosystem": "vendor"}, {"name": "microsoft windows 10 22h2", "fixed": ["10.0.19045.6456"], "affected": "< 10.0.19045.6456", "ecosystem": "vendor"}, {"name": "microsoft windows 11 22h2", "fixed": ["10.0.22621.6060"], "affected": "< 10.0.22621.6060", "ecosystem": "vendor"}, {"name": "microsoft windows 11 23h2", "fixed": ["10.0.22631.6060"], "affected": "< 10.0.22631.6060", "ecosystem": "vendor"}, {"name": "microsoft windows 11 24h2", "fixed": ["10.0.26100.6899"], "affected": "< 10.0.26100.6899", "ecosystem": "vendor"}, {"name": "microsoft windows 11 25h2", "fixed": ["10.0.26200.6899"], "affected": "< 10.0.26200.6899", "ecosystem": "vendor"}, {"name": "microsoft windows server 2012", "fixed": [], "affected": "", "ecosystem": "vendor"}, {"name": "microsoft windows server 2012", "fixed": [], "affected": "= r2", "ecosystem": "vendor"}, {"name": "microsoft windows server 2016", "fixed": ["10.0.14393.8519"], "affected": "< 10.0.14393.8519", "ecosystem": "vendor"}, {"name": "microsoft windows server 2019", "fixed": ["10.0.17763.7919"], "affected": "< 10.0.17763.7919", "ecosystem": "vendor"}, {"name": "microsoft windows server 2022", "fixed": ["10.0.20348.4294"], "affected": "< 10.0.20348.4294", "ecosystem": "vendor"}, {"name": "microsoft windows server 2022 23h2", "fixed": ["10.0.25398.1913"], "affected": "< 10.0.25398.1913", "ecosystem": "vendor"}, {"name": "microsoft windows server 2025", "fixed": ["10.0.26100.6899"], "affected": "< 10.0.26100.6899", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["endpoints", "exploited", "igel-os", "infrastructure", "thin-clients"]
not_affected_if: ["unknown"]
published_at: "2025-06-05T14:15:32+00:00"
first_seen_at: "2026-10-23T19:11:51+00:00"
updated_at: "2026-10-23T23:44:51+00:00"
sources: [{"source": "kev", "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-47827", "first_seen_at": "2026-10-23T19:11:51+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-47827", "first_seen_at": "2026-10-23T23:44:51+00:00"}]
---

# In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a…

IGEL OS, the thin-client operating system, has a flaw where an expired signing key is still accepted, letting an attacker bypass Secure Boot. A crafted root filesystem image can then be mounted without verification, which means attacker-controlled code can run during boot.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:IGEL IGEL OS affected ? fixed ?
- vendor:igel os affected < 11.01.100 fixed 11.01.100
- vendor:microsoft windows 10 1507 affected < 10.0.10240.21161 fixed 10.0.10240.21161
- vendor:microsoft windows 10 1607 affected < 10.0.14393.8519 fixed 10.0.14393.8519
- vendor:microsoft windows 10 1809 affected < 10.0.17763.7919 fixed 10.0.17763.7919
- vendor:microsoft windows 10 21h2 affected < 10.0.19044.6456 fixed 10.0.19044.6456
- vendor:microsoft windows 10 22h2 affected < 10.0.19045.6456 fixed 10.0.19045.6456
- vendor:microsoft windows 11 22h2 affected < 10.0.22621.6060 fixed 10.0.22621.6060
- vendor:microsoft windows 11 23h2 affected < 10.0.22631.6060 fixed 10.0.22631.6060
- vendor:microsoft windows 11 24h2 affected < 10.0.26100.6899 fixed 10.0.26100.6899
- vendor:microsoft windows 11 25h2 affected < 10.0.26200.6899 fixed 10.0.26200.6899
- vendor:microsoft windows server 2012 affected ? fixed ?
- vendor:microsoft windows server 2012 affected = r2 fixed ?
- vendor:microsoft windows server 2016 affected < 10.0.14393.8519 fixed 10.0.14393.8519
- vendor:microsoft windows server 2019 affected < 10.0.17763.7919 fixed 10.0.17763.7919
- vendor:microsoft windows server 2022 affected < 10.0.20348.4294 fixed 10.0.20348.4294
- vendor:microsoft windows server 2022 23h2 affected < 10.0.25398.1913 fixed 10.0.25398.1913
- vendor:microsoft windows server 2025 affected < 10.0.26100.6899 fixed 10.0.26100.6899

## Fix

Apply the mitigation from the IGEL vendor advisory, as CISA directs; the sources do not name a fixed version.
If no mitigation exists, CISA says to discontinue use of the product.

## Timeline

- 2026-10-23T19:11:51+00:00 kev https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-47827
- 2026-10-23T23:44:51+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-47827

## From the sources

IGEL OS contains a use of a key past its expiration date vulnerability that allows for Secure Boot bypass. The igel-flash-driver module improperly verifies a cryptographic signature. Ultimately, a crafted root filesystem can be mounted from an unverified SquashFS image.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_