CVE-2025-47827
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.
At a glance
- Exploitability
- Can be exploited with physical access without logging in. High risk of service disruption.
- In the wild
- CISA lists this as exploited in real attacks. Treat as urgent.
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- 2025-10-14 Exploited in the wildAdded to CISA's Known Exploited Vulnerabilities list
- 2025-11-04 Remediation deadlineCISA's due date for federal agencies to fix it
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: yes, CISA lists it. This puts it above everything that is not.
- Exploit odds: 5.2% in the next 30 days (EPSS).
- Severity: 4.6 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Added to CISA KEV
- 2025-10-14
- Exploit probability
- 5.2% · EPSS, next 30 days
- Weakness
- CWE-347
- Record status
- Analyzed
Affected
- Igel Os < 11.01.100
- Microsoft Windows 10 1507 < 10.0.10240.21161
- Microsoft Windows 10 1607 < 10.0.14393.8519
- Microsoft Windows 10 1809 < 10.0.17763.7919
- Microsoft Windows 10 21h2 < 10.0.19044.6456
- Microsoft Windows 10 22h2 < 10.0.19045.6456
- Microsoft Windows 11 22h2 < 10.0.22621.6060
- Microsoft Windows 11 23h2 < 10.0.22631.6060
Attack profile CVSS 3.1 · 4.6
- Attack vector
- Physical
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-47827.md and follow it. Check whether this project is affected by CVE-2025-47827. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
