CVERadar
MEDIUM · CVSS 3.1 4.6CISA KEV · added 2025-10-14EPSS 4.93% (p92)Threat level 39

CVE-2025-47827: IGEL OS Use of a Key Past its Expiration Date Vulnerability

IGEL · IGEL OS · NVD published 2025-06-05 · posted 2025-10-14 · last modified 2026-06-17

What it is

In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a cryptographic signature. Ultimately, a crafted root filesystem can be mounted from an unverified SquashFS image.

WeaknessCWE-347CWE-324
CVSS vectorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
CISA due date2025-11-04 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsDefense Impairment

Exploitation evidence

First exploit evidence seen: 2025-10-14 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2025-10-14. Source

Public exploit code

GitHub proof-of-concept repositories below quality bar

1 public repositories from 1 accounts, first seen 2025-06-05.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

Defend the Chain

The attack chain for CVE-2025-47827 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 39/100
Defender level 1 · 0 XP
Chain links broken: 0/1

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Stealth

Defense Impairment

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1553 Subvert Trust Controls Inferred

Inferred from CWE CWE-347

How to fix it

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. (source: CISA KEV)

Fixed versions

  • igel igel os: upgrade to 11.01.100 or later
  • microsoft windows 10 1507: upgrade to 10.0.10240.21161 or later
  • microsoft windows 10 1607: upgrade to 10.0.14393.8519 or later
  • microsoft windows 10 1809: upgrade to 10.0.17763.7919 or later
  • microsoft windows 10 21h2: upgrade to 10.0.19044.6456 or later
  • microsoft windows 10 22h2: upgrade to 10.0.19045.6456 or later
  • microsoft windows 11 22h2: upgrade to 10.0.22621.6060 or later
  • microsoft windows 11 23h2: upgrade to 10.0.22631.6060 or later
  • microsoft windows 11 24h2: upgrade to 10.0.26100.6899 or later
  • microsoft windows 11 25h2: upgrade to 10.0.26200.6899 or later
  • microsoft windows server 2016: upgrade to 10.0.14393.8519 or later
  • microsoft windows server 2019: upgrade to 10.0.17763.7919 or later
  • microsoft windows server 2022: upgrade to 10.0.20348.4294 or later
  • microsoft windows server 2022 23h2: upgrade to 10.0.25398.1913 or later
  • microsoft windows server 2025: upgrade to 10.0.26100.6899 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1038 Execution Prevention (for T1553) : System settings can prevent applications from running that haven't been downloaded through the Apple Store (or other legitimate repositories) which can help mitigate some of these issues. Also enable application control solutions such as AppLocker and/or Device Guard to block the loading of malicious content.
  • M1028 Operating System Configuration (for T1553) : Windows Group Policy can be used to manage root certificates and the <code>Flags</code> value of <code>HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\Root\\ProtectedRoots</code> can be set to 1 to prevent non-administrator users from making further root installations into their own HKCU certificate store.
  • M1026 Privileged Account Management (for T1553) : Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
  • M1024 Restrict Registry Permissions (for T1553) : Ensure proper permissions are set for Registry hives to prevent users from modifying keys related to SIP and trust provider components. Components may still be able to be hijacked to suitable functions already present on disk if malicious modifications to Registry keys are not prevented.
  • M1054 Software Configuration (for T1553) : HTTP Public Key Pinning (HPKP) is one method to mitigate potential [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1557) situations where and adversary uses a mis-issued or fraudulent certificate to intercept encrypted communications by enforcing use of an expected certificate.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources