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.
CVE-2025-47827
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-10-14), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 4.6 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.6
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 5%
- EPSS %ILE
- 92%
- KEV
- ⚠ Exploited
Published
June 5, 2025
Last Modified
November 5, 2025
Advisory Details (4)
Auto-updated Jun 13, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-47827Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2025-47827GitHub - Zedeldi/CVE-2025-47827: PoC and vulnerability report for CVE-2025-47827. · GitHub
https://github.com/Zedeldi/CVE-2025-47827GitHub - Zedeldi/igelfs: Python implementation of the IGEL filesystem. · GitHub
https://github.com/Zedeldi/igelfsWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 95× in last 7d / 395× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,423 total refreshes for this CVE.
- 2026-09-19 21:49 UTCVendor advisory
- 2026-09-19 21:49 UTCGHSA enrichment
- 2026-09-19 17:34 UTCEG score recompute
- 2026-09-19 17:34 UTCVendor advisory
- 2026-09-19 17:34 UTCGHSA enrichment
- 2026-09-19 13:19 UTCVendor advisory
- 2026-09-19 13:19 UTCGHSA enrichment
- 2026-09-19 09:04 UTCVendor advisory
- 2026-09-19 09:04 UTCGHSA enrichment
- 2026-09-19 04:50 UTCVendor advisory
- 2026-09-19 04:50 UTCGHSA enrichment
- 2026-09-19 00:34 UTCVendor advisory
- 2026-09-19 00:34 UTCGHSA enrichment
- 2026-09-18 20:19 UTCEG score recompute
- 2026-09-18 20:19 UTCVendor advisory
- 2026-09-18 20:19 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 16:05 UTCVendor advisory
- 2026-09-18 16:05 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 11:49 UTCVendor advisory
- 2026-09-18 11:49 UTCGHSA enrichment
- 2026-09-18 07:34 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-18 07:34 UTCGHSA enrichment
- 2026-09-18 03:19 UTCVendor advisory
- 2026-09-18 03:19 UTCGHSA enrichment
- 2026-09-17 23:04 UTCEG score recompute
- 2026-09-17 23:04 UTCVendor advisory
- 2026-09-17 23:04 UTCGHSA enrichment
- 2026-09-17 19:29 UTCEPSS rescore
- 2026-09-17 18:49 UTCVendor advisory
- 2026-09-17 18:49 UTCGHSA enrichment
- 2026-09-17 14:35 UTCVendor advisory
- 2026-09-17 14:35 UTCGHSA enrichment
- 2026-09-17 10:20 UTCVendor advisory
- 2026-09-17 10:20 UTCGHSA enrichment
- 2026-09-17 06:05 UTCVendor advisory
- 2026-09-17 06:05 UTCGHSA enrichment
- 2026-09-17 01:50 UTCVendor advisory
- 2026-09-17 01:50 UTCGHSA enrichment
- 2026-09-16 21:35 UTCVendor advisory
- 2026-09-16 21:35 UTCGHSA enrichment
- 2026-09-16 17:20 UTCEG score recompute
- 2026-09-16 17:20 UTCVendor advisory
- 2026-09-16 17:20 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 13:04 UTCVendor advisory
- 2026-09-16 13:04 UTCGHSA enrichment
- 2026-09-16 08:50 UTCEG score recompute
- 2026-09-16 08:50 UTCVendor advisory
- 2026-09-16 08:50 UTCGHSA enrichment
- 2026-09-16 04:35 UTCVendor advisory
- 2026-09-16 04:35 UTCGHSA enrichment
- 2026-09-16 00:20 UTCVendor advisory
- 2026-09-16 00:20 UTCGHSA enrichment
- 2026-09-15 20:06 UTCVendor advisory
- 2026-09-15 20:06 UTCGHSA enrichment
- 2026-09-15 15:51 UTCVendor advisory
- 2026-09-15 15:51 UTCGHSA enrichment
- 2026-09-15 11:36 UTCVendor advisory
- 2026-09-15 11:36 UTCGHSA enrichment
- 2026-09-15 07:21 UTCEG score recompute
- 2026-09-15 07:21 UTCVendor advisory
- 2026-09-15 07:21 UTCGHSA enrichment
- 2026-09-15 03:09 UTCEPSS rescore
- 2026-09-15 03:06 UTCGHSA enrichment
- 2026-09-14 22:51 UTCVendor advisory
- 2026-09-14 22:51 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 18:36 UTCVendor advisory
- 2026-09-14 18:36 UTCGHSA enrichment
- 2026-09-14 14:21 UTCVendor advisory
- 2026-09-14 14:21 UTCGHSA enrichment
- 2026-09-14 10:06 UTCVendor advisory
- 2026-09-14 10:06 UTCGHSA enrichment
- 2026-09-14 05:51 UTCVendor advisory
- 2026-09-14 05:51 UTCGHSA enrichment
- 2026-09-14 01:37 UTCVendor advisory
- 2026-09-14 01:37 UTCGHSA enrichment
- 2026-09-13 21:22 UTCVendor advisory
- 2026-09-13 21:22 UTCGHSA enrichment
- 2026-09-13 17:07 UTCEG score recompute
- 2026-09-13 17:07 UTCVendor advisory
- 2026-09-13 17:07 UTCGHSA enrichment
- 2026-09-13 12:52 UTCVendor advisory
- 2026-09-13 12:52 UTCGHSA enrichment
- 2026-09-13 08:38 UTCVendor advisory
- 2026-09-13 08:38 UTCGHSA enrichment
- 2026-09-13 04:23 UTCVendor advisory
- 2026-09-13 04:23 UTCGHSA enrichment
- 2026-09-13 00:08 UTCVendor advisory
- 2026-09-13 00:08 UTCGHSA enrichment
- 2026-09-12 19:53 UTCVendor advisory
- 2026-09-12 19:53 UTCGHSA enrichment
- 2026-09-12 15:38 UTCEG score recompute
- 2026-09-12 15:38 UTCVendor advisory
- 2026-09-12 15:38 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCZedeldi/CVE-2025-47827First seen May 20, 2025
PoC and vulnerability report for CVE-2025-47827.
Open source ↗
Frequently asked(6)
What is CVE-2025-47827?
When was CVE-2025-47827 disclosed?
Is CVE-2025-47827 actively exploited?
What is the CVSS score of CVE-2025-47827?
Which products are affected by CVE-2025-47827?
How do I remediate CVE-2025-47827?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-47827
Is Your Infrastructure Affected by CVE-2025-47827?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.