CVE-2025-47827
IGEL OS Use of a Key Past its Expiration Date
- Published5 Jun 2025
- Added to CISA KEV14 Oct 2025
- Remediation due4 Nov 2025
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-47827 being actively exploited?
Yes. CVE-2025-47827 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 14 Oct 2025.
How severe is CVE-2025-47827?
CVE-2025-47827 has a CVSS 3.1 base score of 4.6, rated medium. EPSS estimates a 4.93% probability of exploitation.
Which products are affected by CVE-2025-47827?
Affected products include Igel OS, Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, and 11 more.
How do I fix CVE-2025-47827?
Upgrade affected software to a fixed version, for example Igel OS 11.01.100, Microsoft Windows 10 1507 10.0.10240.21161, Microsoft Windows 10 1607 10.0.14393.8519 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-47827 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.