Skip to content
CTI Academy Sponsor CTI Academy
MEDIUM · CVSS 4.6 CISA Known Exploited Vulnerability

CVE-2025-47827

IGEL OS Use of a Key Past its Expiration Date Vulnerability

IGEL OS

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
4.6
MEDIUM
EPSS
5.2%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
5 Jun 2025
CWE-347

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 14 October 2025. US federal agencies were required to remediate it by 4 November 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 5.2%, which is higher than 92.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Frequently asked questions

Is CVE-2025-47827 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2025-47827.

What does CVE-2025-47827 affect?

CVE-2025-47827 affects IGEL OS. 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.

How severe is CVE-2025-47827?

CVE-2025-47827 is rated MEDIUM with a CVSS base score of 4.6. EPSS puts the probability of exploitation in the next 30 days at 5.2%, higher than 92.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 4 November 2025.

How should organisations respond to CVE-2025-47827?

Apply the vendor patch for IGEL OS as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.