What is CVE-2025-47827?A medium-severity flaw criminals are using now.
CVE-2025-47827 is a medium-severity flaw (CVSS 4.6) in Igel OS, published on 5 June 2025. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 4.9%. If you run an affected version, patch it first.
Published 5 June 2025. Record last updated 15 October 2025. We keep this page's data up to date.
What is CVE-2025-47827? In plain terms.
An attacker has to be physically at the device without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
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.
What kind of flaw is it?
- CWE-347Improper Verification of Cryptographic Signature
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can bePhysically at the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2025-47827 being exploited? Yes.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 4.9%.
Timeline
- Published
- Added to the known-exploited list
- Record last updated
- Exploit likelihood jumped
- Exploit likelihood fell
CVE-2025-47827 scores 74. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2025-47827 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2025-47827? 16 products.
The published record lists 16 products from 2 vendors. Versions are shown as published: "before 11.01.100" means every version up to, but not including, 11.01.100. If you run one of these, check your version, then go to the fix below.
- Operating system
Igel OS
by Igel
Affected versionsbefore 11.01.100 - Operating system
Windows 10 1507
by Microsoft
Affected versionsbefore 10.0.10240.21161 - Operating system
Windows 10 1607
by Microsoft
Affected versionsbefore 10.0.14393.8519 - Operating system
Windows 10 1809
by Microsoft
Affected versionsbefore 10.0.17763.7919 - Operating system
Windows 10 21H2
by Microsoft
Affected versionsbefore 10.0.19044.6456 - Operating system
Windows 10 22H2
by Microsoft
Affected versionsbefore 10.0.19045.6456 - Operating system
Windows 11 22H2
by Microsoft
Affected versionsbefore 10.0.22621.6060 - Operating system
Windows 11 23H2
by Microsoft
Affected versionsbefore 10.0.22631.6060 - Operating system
Windows 11 24H2
by Microsoft
Affected versionsbefore 10.0.26100.6899
How do I fix CVE-2025-47827? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
Does CVE-2025-47827 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a cryptographic signature. Ultimately, a crafted r...
- Matched to
- Igel OS on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2025-47827 is a medium-severity flaw in Igel OS, published on 5 June 2025. An attacker has to be physically at the device without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 4.6 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2025-47827 is 74 out of 100, which is High. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 4.9%.
For Igel OS: before 11.01.100. The record lists 16 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.