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
- 89.5%
- 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 84× in last 7d / 384× 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 689 total refreshes for this CVE.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 02:57 UTCEG score recompute
- 2026-07-22 20:38 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:21 UTCEG score recompute
- 2026-07-22 16:21 UTCVendor advisory
- 2026-07-22 16:21 UTCGHSA enrichment
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 12:06 UTCVendor advisory
- 2026-07-22 12:06 UTCGHSA enrichment
- 2026-07-22 07:51 UTCVendor advisory
- 2026-07-22 07:51 UTCGHSA enrichment
- 2026-07-22 03:36 UTCVendor advisory
- 2026-07-22 03:36 UTCGHSA enrichment
- 2026-07-21 23:22 UTCVendor advisory
- 2026-07-21 23:21 UTCGHSA enrichment
- 2026-07-21 17:27 UTCEG score recompute
- 2026-07-21 17:27 UTCVendor advisory
- 2026-07-21 17:27 UTCGHSA enrichment
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:11 UTCVendor advisory
- 2026-07-21 13:11 UTCGHSA enrichment
- 2026-07-21 08:57 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-21 08:57 UTCGHSA enrichment
- 2026-07-21 04:41 UTCVendor advisory
- 2026-07-21 04:41 UTCGHSA enrichment
- 2026-07-21 00:26 UTCVendor advisory
- 2026-07-21 00:26 UTCGHSA enrichment
- 2026-07-20 20:12 UTCEG score recompute
- 2026-07-20 20:12 UTCVendor advisory
- 2026-07-20 20:11 UTCGHSA enrichment
- 2026-07-20 17:07 UTCEPSS rescore
- 2026-07-20 15:57 UTCGHSA enrichment
- 2026-07-20 11:42 UTCGHSA enrichment
- 2026-07-20 07:27 UTCVendor advisory
- 2026-07-20 07:27 UTCGHSA enrichment
- 2026-07-20 03:13 UTCVendor advisory
- 2026-07-20 03:12 UTCGHSA enrichment
- 2026-07-19 22:58 UTCVendor advisory
- 2026-07-19 22:58 UTCGHSA enrichment
- 2026-07-19 18:43 UTCEG score recompute
- 2026-07-19 18:43 UTCVendor advisory
- 2026-07-19 18:43 UTCGHSA enrichment
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:28 UTCVendor advisory
- 2026-07-19 14:28 UTCGHSA enrichment
- 2026-07-19 10:14 UTCVendor advisory
- 2026-07-19 10:14 UTCGHSA enrichment
- 2026-07-19 05:59 UTCEG score recompute
- 2026-07-19 05:59 UTCVendor advisory
- 2026-07-19 05:59 UTCGHSA enrichment
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 01:43 UTCGHSA enrichment
- 2026-07-18 21:28 UTCVendor advisory
- 2026-07-18 21:28 UTCGHSA enrichment
- 2026-07-18 17:13 UTCVendor advisory
- 2026-07-18 17:13 UTCGHSA enrichment
- 2026-07-18 12:58 UTCEG score recompute
- 2026-07-18 12:58 UTCVendor advisory
- 2026-07-18 12:58 UTCGHSA enrichment
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 08:43 UTCVendor advisory
- 2026-07-18 08:43 UTCGHSA enrichment
- 2026-07-18 04:28 UTCVendor advisory
- 2026-07-18 04:28 UTCGHSA enrichment
- 2026-07-18 00:13 UTCVendor advisory
- 2026-07-18 00:13 UTCGHSA enrichment
- 2026-07-17 19:58 UTCVendor advisory
- 2026-07-17 19:58 UTCGHSA enrichment
- 2026-07-17 15:43 UTCVendor advisory
- 2026-07-17 15:43 UTCGHSA enrichment
- 2026-07-17 11:28 UTCVendor advisory
- 2026-07-17 11:28 UTCGHSA enrichment
- 2026-07-17 07:13 UTCEG score recompute
- 2026-07-17 07:13 UTCVendor advisory
- 2026-07-17 07:13 UTCGHSA enrichment
- 2026-07-17 02:58 UTCVendor advisory
- 2026-07-17 02:58 UTCGHSA enrichment
- 2026-07-16 22:44 UTCVendor advisory
- 2026-07-16 22:44 UTCGHSA enrichment
- 2026-07-16 18:29 UTCVendor advisory
- 2026-07-16 18:29 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 14:15 UTCVendor advisory
- 2026-07-16 14:15 UTCGHSA enrichment
- 2026-07-16 10:00 UTCGHSA enrichment
- 2026-07-16 05:46 UTCVendor advisory
- 2026-07-16 05:46 UTCGHSA enrichment
- 2026-07-16 01:31 UTCVendor advisory
- 2026-07-16 01:31 UTCGHSA enrichment
- 2026-07-15 21:16 UTCVendor advisory
- 2026-07-15 21:16 UTCGHSA enrichment
- 2026-07-15 17:02 UTCVendor advisory
- 2026-07-15 17:01 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.