NVD / CVE Program· CNA mitre

CVE-2025-47827: In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a cryptographic signature.

MediumCVSS 4.6 · v3.1KEVWeaponized Fix available

Noroxi assessment

Priority: Plan (action score 50/100)

CISA has confirmed exploitation in the wild (Oct 14, 2025). Remediation deadline for US federal agencies: Nov 4, 2025.
Probability of exploitation in the next 30 days: 5.1% (FIRST EPSS); higher than 92.5% of all records.
Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Windows 10 for 32-bit Systems 10.0.10240.21161; Windows 10 for x64-based Systems 10.0.10240.21161; Windows 10 Version 1607 for 32-bit Systems 10.0.14393.8519.

Add it to your regular patch cycle. Upgrade to Windows 10 for 32-bit Systems 10.0.10240.21161; Windows 10 for x64-based Systems 10.0.10240.21161; Windows 10 Version 1607 for 32-bit Systems 10.0.14393.8519 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

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.

BDU:2025-12993

Published: Jun 5, 2025
Updated: Jun 17, 2026
EPSS: 5.1% · 92th percentile
CWE: CWE-347

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 18 / 40 · 4.6 / 10
CISA KEV: 30 / 30 · Listed
EPSS: 2 / 30 · 5.1%

CISA SSVC decision

Exploitation: active
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Oct 14, 2025. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Nov 4, 2025.

Get told when this record changes

In CISA KEV: exploitation in the wild confirmed
Weaponized exploit exists
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
igel	igel os	cpe:2.3:o:igel:igel_os
microsoft	windows 10 1507	cpe:2.3:o:microsoft:windows_10_1507
microsoft	windows 10 1607	cpe:2.3:o:microsoft:windows_10_1607
microsoft	windows 10 1809	cpe:2.3:o:microsoft:windows_10_1809
microsoft	windows 10 21h2	cpe:2.3:o:microsoft:windows_10_21h2
microsoft	windows 10 22h2	cpe:2.3:o:microsoft:windows_10_22h2
microsoft	windows 11 22h2	cpe:2.3:o:microsoft:windows_11_22h2
microsoft	windows 11 23h2	cpe:2.3:o:microsoft:windows_11_23h2
microsoft	windows 11 24h2	cpe:2.3:o:microsoft:windows_11_24h2
microsoft	windows 11 25h2	cpe:2.3:o:microsoft:windows_11_25h2
microsoft	windows server 2012	cpe:2.3:o:microsoft:windows_server_2012
microsoft	windows server 2016	cpe:2.3:o:microsoft:windows_server_2016

and 4 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

microsoft windows server 2012all versions
microsoft windows server 2012r2
microsoft windows server 2016before 10.0.14393.8519
microsoft windows server 2019before 10.0.17763.7919
microsoft windows server 2022before 10.0.20348.4294
microsoft windows server 2022 23h2before 10.0.25398.1913
microsoft windows server 2025before 10.0.26100.6899

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Windows 10 for 32-bit Systems	10.0.10240.21161 · KB5066837	Microsoft (MSRC)
Windows 10 for x64-based Systems	10.0.10240.21161 · KB5066837	Microsoft (MSRC)
Windows 10 Version 1607 for 32-bit Systems	10.0.14393.8519 · KB5066836	Microsoft (MSRC)
Windows 10 Version 1607 for x64-based Systems	10.0.14393.8519 · KB5066836	Microsoft (MSRC)
Windows 10 Version 1809 for 32-bit Systems	10.0.17763.7919 · KB5066586	Microsoft (MSRC)
Windows 10 Version 1809 for x64-based Systems	10.0.17763.7919 · KB5066586	Microsoft (MSRC)
Windows 10 Version 21H2 for 32-bit Systems	10.0.19044.6456 · KB5066791	Microsoft (MSRC)
Windows 10 Version 21H2 for ARM64-based Systems	10.0.19044.6456 · KB5066791	Microsoft (MSRC)
Windows 10 Version 21H2 for x64-based Systems	10.0.19044.6456 · KB5066791	Microsoft (MSRC)
Windows 10 Version 22H2 for 32-bit Systems	10.0.19045.6456 · KB5066791	Microsoft (MSRC)
Windows 10 Version 22H2 for ARM64-based Systems	10.0.19045.6456 · KB5066791	Microsoft (MSRC)
Windows 10 Version 22H2 for x64-based Systems	10.0.19045.6456 · KB5066791	Microsoft (MSRC)
Windows 11 Version 22H2 for ARM64-based Systems	10.0.22621.6060 · KB5066793	Microsoft (MSRC)
Windows 11 Version 22H2 for x64-based Systems	10.0.22621.6060 · KB5066793	Microsoft (MSRC)
Windows 11 Version 23H2 for ARM64-based Systems	10.0.22631.6060 · KB5066793	Microsoft (MSRC)
Windows 11 Version 23H2 for x64-based Systems	10.0.22631.6060 · KB5066793	Microsoft (MSRC)
Windows 11 Version 24H2 for ARM64-based Systems	10.0.26100.6899 · KB5066835	Microsoft (MSRC)
Windows 11 Version 24H2 for x64-based Systems	10.0.26100.6899 · KB5066835	Microsoft (MSRC)
Windows 11 Version 25H2 for ARM64-based Systems	10.0.26200.6899 · KB5066835	Microsoft (MSRC)
Windows 11 Version 25H2 for x64-based Systems	10.0.26200.6899 · KB5066835	Microsoft (MSRC)
Windows Server 2012	6.2.9200.25722 · KB5066875	Microsoft (MSRC)
Windows Server 2012 (Server Core installation)	6.2.9200.25722 · KB5066875	Microsoft (MSRC)
Windows Server 2012 R2	6.3.9600.22824 · KB5066873	Microsoft (MSRC)
Windows Server 2012 R2 (Server Core installation)	6.3.9600.22824 · KB5066873	Microsoft (MSRC)
Windows Server 2016	10.0.14393.8519 · KB5066836	Microsoft (MSRC)
Windows Server 2016 (Server Core installation)	10.0.14393.8519 · KB5066836	Microsoft (MSRC)
Windows Server 2019	10.0.17763.7919 · KB5066586	Microsoft (MSRC)
Windows Server 2019 (Server Core installation)	10.0.17763.7919 · KB5066586	Microsoft (MSRC)
Windows Server 2022	10.0.20348.4294 · KB5066782	Microsoft (MSRC)
Windows Server 2022 (Server Core installation)	10.0.20348.4294 · KB5066782	Microsoft (MSRC)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:4	2025-05-20

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

First PoCMay 20, 2025-16 d
PublishedJun 5, 2025
CISA KEVOct 14, 2025+131 d
TodayNov 14, 2026+527 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Physical access to the device is required.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Physical
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

The bug in code

The whole CWE-347 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const claims = jwt.verify(token, publicKey);

Fixed

1const claims = jwt.verify(token, publicKey, {
2  algorithms: ["RS256"],
3  issuer: "https://id.example.com",
4  audience: "portal",
5});

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 30, 2026, 3:27 AM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/Zedeldi/igelfs

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records