CVE-2025-47827
Exploited in the wild. In CISA KEV since 2025‑10‑14. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- Igel OsAffected: < 11.01.100Upgrade to: 11.01.100Stated by: NVD
- Microsoft Windows 10 1507Affected: < 10.0.10240.21161Upgrade to: 10.0.10240.21161Affected: < 10.0.14393.8519Upgrade to: 10.0.14393.8519Affected: < 10.0.17763.7919Upgrade to: 10.0.17763.7919Affected: < 10.0.19044.6456Upgrade to: 10.0.19044.6456 + 1 more branchStated by: NVD
- Microsoft Windows 11 22h2Affected: < 10.0.22621.6060Upgrade to: 10.0.22621.6060Affected: < 10.0.22631.6060Upgrade to: 10.0.22631.6060Affected: < 10.0.26100.6899Upgrade to: 10.0.26100.6899Affected: < 10.0.26200.6899Upgrade to: 10.0.26200.6899Stated by: NVD
- Microsoft Windows Server 2016Affected: < 10.0.14393.8519Upgrade to: 10.0.14393.8519Stated by: NVD
- Microsoft Windows Server 2019Affected: < 10.0.17763.7919Upgrade to: 10.0.17763.7919Stated by: NVD
Versions as the sources state them. 4 more products have version data. Full version matrix after sign-in
Coverage timeline
0 publishersAdded to CISA KEV catalog
Sourced from public security reporting — each date is when it was published, not when it happened.
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2025-10-14.
US federal agencies must remediate by 2025-11-04.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- Public exploits
2 sources with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
4.9% chance of exploitation activity in the next 30 days, which ranks it in the 92nd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 121 days before any public exploit.
- OpenVAS check added
- Public exploit / PoCsource: github-poc
- Patch availablerecord updated
- Added to CISA KEV
- Publishedweakness classified, att&ck mapped
Affected products
- Windows 10 1607Operating Systems / windows
- Windows 11 24H2Operating Systems / windows
- Windows Server 2012 (Server Core installation)Operating Systems / windows
- Windows Server 2016 (Server Core installation)Operating Systems / windows
- Windows Server 2019 (Server Core installation)Operating Systems / windows
- Windows Server 2022, 23H2 Edition (Server Core installation)Operating Systems / windows
- Windows Server 2025 (Server Core installation)Operating Systems / windows
- Windows Server 2012 R2 (Server Core installation)Operating Systems / windows
And 30 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 4.6 by NVD.
How it is reached
- Attack Vector PhysicalRequires physical access to the device
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- github.com/Zedeldi/igelfs
- github.com/Zedeldi/CVE-2025-47827
- msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2025-47827
And 5 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Windows 10 1607, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI