What is CVE-2025-47827?

CVE-2025-47827 is IGEL OS Use of a Key Past its Expiration Date Vulnerability. The supplied enrichment data classifies it as Unclassified mapped to CWE-347 CWE-347.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

3 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-47827 using CVSS 4.6, EPSS 4%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Rocke (), Infy (), Mana Team (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVmediumpublic exploit

CVE-2025-47827

CVE-2025-47827 — IGEL OS Use of a Key Past its Expiration Date Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-47827 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Jun 5, 2025Updated Jun 17, 2026Sources: NVD, IGEL (CNA), CISA, FIRST EPSS, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Oct 14, 2025

EPSS

ahead of 90% of scored CVEs

Affects

IGEL

IGEL OS

CVSS base

4.6

medium

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade IGEL OS to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Nov 4, 2025 — passed 318 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
IGEL	IGEL OS	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

None

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Physical

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
4.6	CVSS 3.1	medium	0.9	3.6	CNA

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-347 · Improper Verification of Cryptographic Signature

Gain Privileges or Assume Identity
Modify Application Data
Execute Unauthorized Code or Commands

Weakness & attack patterns

CWE-347

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-463 · Padding Oracle Crypto AttackCAPEC-475 · Signature Spoofing by Improper Validation

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Oct 14, 2025

Federal deadline

Nov 4, 2025

passed 318 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

RockeInfyMana Team

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 4.6 (AV:P)
Jun 17, 2026 · NVD
2025
Bulletin released on NIST.
Oct 16, 2025 · SOCRadar CTI
Bulletin released on NIST.
Oct 16, 2025 · SOCRadar CTI
Cve is exploited IGEL OS Use of a Key Past its Expiration Date Vulnerability
Oct 15, 2025 · SOCRadar CTI
Bulletin released on NIST.
Oct 15, 2025 · SOCRadar CTI
Bulletin released on NIST.
Oct 15, 2025 · SOCRadar CTI
Bulletin released on NIST.
Oct 15, 2025 · SOCRadar CTI
Bulletin released on NIST.
Oct 15, 2025 · SOCRadar CTI
Added to CISA KEV catalog
Oct 14, 2025 · CISA
Initial · CVE published
Jun 5, 2025 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

10×SVRS was changedAug 9, 2025 – Nov 10, 2025 · SOCRadar CTI
9×TweetsJul 19, 2025 – Oct 26, 2025 · SOCRadar CTI
1×1 time mentioned on 1 Telegram channelOct 16, 2025 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Oct 15, 2025 · SOCRadar CTI
1×CVE modified by NIST: CISA KEV details updated.Oct 15, 2025 · SOCRadar CTI

References

5 on the record

github.com/Zedeldi/CVE-2025-47827
Exploit, Third Party Advisory, NIST, GITHUB
github.com/Zedeldi/igelfs
Product, NIST
msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2025-47827
Third Party Advisory, NIST, Vendor Advisory
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-47827
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2025-47827
Vendor Advisory

Coverage

17 stories from the feeds we poll

12 more reports on this CVEShowing 5 of 17 · Vendor research and security press coverageUnlock free

Elsewhere on this site

IGELevery CVE for this vendor
October 2025what else CISA listed
Unclassifiedsame class
CWE-347other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-47827 is IGEL OS Use of a Key Past its Expiration Date Vulnerability, a medium vulnerability affecting IGEL OS from IGEL. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 3 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4.6 describes technical severity, while EPSS 4% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.