CVE-2025-20614
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to computing improvement program 2.4.11001 or later upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
External control of file name or path 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 a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
- weakness
- Escalation of Privilege; CWE-73 External Control of File Name or Path
- affected
- n/a Intel(R) CIP software
- published ranges
- intel computing improvement program < 2.4.11001
- first unaffected version, by branch
- computing improvement program 2.4.11001
- severity
- 5.6 CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- assigned by
- intel
- published
- 2025-11-11
check us intel.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 12 Nov 2025 | 0.00012 | |
| 17 Nov 2025 | 0.00015 | |
| 13 Dec 2025 | 0.00016 | |
| 18 Jan 2026 | 0.00017 | |
| 13 Mar 2026 | 0.00021 | |
| 9 Apr 2026 | 0.00014 | |
| 10 Apr 2026 | 0.00013 | |
| 21 Apr 2026 | 0.00015 | |
| 7 Jun 2026 | 0.00017 | |
| 15 Jun 2026 | 0.00123 | scoring model v2026.06.15 |
| 30 Jun 2026 | 0.00126 | |
| 9 Jul 2026 | 0.00138 | |
| 7 Aug 2026 | 0.00141 | |
| 12 Oct 2026 | 0.00151 |
14 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-10-12 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: computing improvement program 2.4.11001. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-20614', '2026-10-30T23:59:59.999999Z', now());