CVE-2025-47827
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack needs physical access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-47827 being exploited?
Yes. CVE-2025-47827 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-47827?
CVE-2025-47827 is rated Medium with a CVSS score of 4.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-47827?
Yes. A fix has been recorded for CVE-2025-47827. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-47827 affect?
CVE-2025-47827 affects igel:igel_os, microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, and 12 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
- Zedeldi/CVE-2025-47827 · 4 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- partial
Assessed by CISA 15 Oct 2025 (SSVC 2.0.3).
timeline
- 20 May 2025First proof-of-concept repository on GitHub (unvetted)
- 5 Jun 2025Published · 17 days later
- 14 Oct 2025Added to CISA KEV (exploited in the wild) · 130 days (about 4 months) later
- 15 Oct 2025CISA SSVC assessment: exploitation active · 1 day later
- 4 Nov 2025CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 115 days (about 4 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Advisorymsrc.microsoft.com /update-guide/en-US/vulnerability/CVE-2025-47827
- Linkgithub.com /Zedeldi/igelfs
- Linkgithub.com /Zedeldi/CVE-2025-47827
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-47827
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.