Skip to main content
Mallory
MediumExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-47827: IGEL OS Boot Signature Verification Bypass

Published Jun 5, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.6Medium · v3.1
EPSS5.2%93rd percentile
CISA KEVYesAdded Oct 14, 2025
In the wildActivePer CISA KEV
Vendors
IgelMicrosoft Corporation
IdentifiersCVE-2025-47827CWE-347 · Improper Verification of…

CVE-2025-47827 is a Secure Boot bypass in IGEL OS versions before 11, notably IGEL OS 10. Improper cryptographic signature verification in the igel-flash-driver kernel module allows a crafted root filesystem from an unverified SquashFS image to be accepted and mounted during boot. An exploit chain can then use kexec to replace the running kernel with an arbitrary untrusted kernel, defeating the device's Secure Boot chain of trust. The defect is in IGEL's downstream kernel behavior, not Shim itself.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation undermines boot integrity and can enable execution of an untrusted kernel, kernel-level rootkit deployment, and persistent root-level access to thin-client endpoints. Compromised endpoints can potentially facilitate credential theft, virtual-desktop session hijacking or tampering, and lateral movement. Exploitation is reported in the wild; the vulnerability is not described as remotely exploitable.

Mitigation

If you can’t patch tonight, do this now.

No complete workaround beyond upgrading is identified. Reduce exposure by restricting physical access, preventing unauthorized removable-media boot, protecting UEFI settings with firmware passwords or management policies, and isolating or retiring devices that cannot be upgraded. Monitor UEFI variable and boot-entry changes, unexpected boot artifacts, kexec usage, and anomalous SquashFS mounts during early boot. These controls do not repair the signature-verification defect.

Remediation

Patch, then assume compromise.

Upgrade affected IGEL OS installations to a maintained release. IGEL OS 11 and 12 are identified as unaffected; recommended maintained-release examples include IGEL OS 11.10.410 or later and IGEL OS 12.7.0 or later. IGEL OS 10 is end-of-maintenance, and upgrading is recommended rather than backporting fixes. Apply applicable Microsoft/OEM Secure Boot DBX revocation updates with staged compatibility testing and recovery planning, since revocations can disrupt booting and may be difficult to reverse.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2025-47827This repository provides a proof-of-concept (PoC) exploit for CVE-2025-47827, a Secure Boot bypass vulnerability in IGEL OS 10 (before v11). The vulnerability arises from improper cryptographic signature verification in the igel-flash-driver kernel module, allowing an attacker to boot a malicious root filesystem from an unverified SquashFS image. The exploit leverages the kexec syscall to replace the running kernel with an attacker-controlled one, either fetched over HTTP or from local disk, thus bypassing Secure Boot and enabling arbitrary code execution at the kernel level. The repository contains several key files: - `mkdiskimage`: A Bash script that automates the process of downloading the official IGEL UDC3 image, extracting and patching the system image, and assembling a bootable disk image with a custom root filesystem or kernel. - `root/sbin/init`: A shell script used as the init process, which parses kernel command-line arguments, fetches or mounts the specified kernel and initrd (supporting both HTTP and local sources), and uses kexec to boot into the attacker-supplied kernel. - `esp/boot/grub/igel.conf`: A GRUB configuration file that defines menu entries for both network and local kexec booting, specifying parameters for kernel, initrd, and command-line arguments. The exploit is primarily local (requires physical or privileged access to the device to modify the boot process), but it also supports network-based payload delivery (fetching kernel/initrd over HTTP). The PoC demonstrates how an attacker can persistently compromise a device by replacing its kernel, effectively rendering Secure Boot protections ineffective on affected IGEL OS systems. The README provides extensive documentation, impact analysis, and references to related resources.Zedeldi · Disclosed May 20, 2025 · bash · sh · local · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
IgelIgel Osoperating_system
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
FAQ

Frequently asked questions

Is CVE-2025-47827 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 14, 2025.
Is there a public exploit for CVE-2025-47827?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-47827, the earliest disclosed May 20, 2025.
Is there a patch for CVE-2025-47827?
Upgrade affected IGEL OS installations to a maintained release. IGEL OS 11 and 12 are identified as unaffected; recommended maintained-release examples include IGEL OS 11.10.410 or later and IGEL OS 12.7.0 or later.
What products are affected by CVE-2025-47827?
Igel Os, Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, and 11 more.
How severe is CVE-2025-47827?
CVE-2025-47827 has a CVSS v3.1 score of 4.6 (Medium) and an EPSS score of 5.2% (93rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

43 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity25Community discussion across Reddit, Mastodon, and other social sources.