Skip to main content
CVE-2025-24299VulnerabilityPublished Updated

CVE-2025-24299: Intel(R) CIP software · Escalation of Privilege

Affects Intel(R) CIP softwareSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High : upgrade to 2.4.0.11001 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0.11001
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Intel(R) CIP software to 2.4.0.11001.

Affected software

ProductAffectedFixed in
Intel(R) CIP softwareAffected
  • <2.4.0.11001
Fixed in
  • 2.4.0.11001

AI-suggested

1. Immediately upgrade Intel(R) CIP software to version WIN_DCA_2.4.0.11001 or later where the vulnerability is patched. 2. Restrict network access to Intel CIP software components to trusted and authenticated users only, employing network segmentation and firewall rules to limit exposure. 3. Implement strict authentication and authorization controls to minimize the number of users with access to vulnerable components. 4. Monitor logs and network traffic for unusual privilege escalation attempts or anomalous behavior related to Intel CIP software. 5. Employ endpoint detection and response (EDR) solutions to detect and block suspicious activities indicative of privilege escalation. 6. Conduct regular vulnerability assessments and penetration testing focused on privilege escalation vectors within the environment. 7. Educate users and administrators about the risks of privilege escalation and the importance of applying patches promptly. 8. If immediate patching is not possible, consider temporary mitigations such as disabling or isolating vulnerable services where feasible.

Description

Improper input validation for some Intel(R) CIP software before version WIN_DCA_2.4.0.11001 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via network access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

References

Community reviews

Loading reviews…