How severe is CVE-2025-20067?

CVE-2025-20067 has a CVSS 3.x base score of 6.0, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-20067 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-20067?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-20067 have an EU (EUVD) identifier?

Yes. CVE-2025-20067 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-24439.

When was CVE-2025-20067 published?

CVE-2025-20067 was published on 2025-08-12 and last updated on 2026-06-17.

CVE-2025-20067

CVE-2025-20067 is a medium-severity vulnerability with a CVSS 3.x base score of 6.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-208.

Key facts

Severity: Medium (CVSS 3.x base score 6.0)
CVSS v4: 6.8
EPSS exploit prediction: 0% (5th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-24439
Weakness: CWE-208
Published: 2025-08-12
Last modified: 2026-06-17

Description

Observable timing discrepancy in firmware for some Intel(R) CSME and Intel(R) SPS may allow a privileged user to potentially enable information disclosure via local access.

Frequently asked questions

What is CVE-2025-20067?: Observable timing discrepancy in firmware for some Intel(R) CSME and Intel(R) SPS may allow a privileged user to potentially enable information disclosure via local access.
How severe is CVE-2025-20067?: CVE-2025-20067 has a CVSS 3.x base score of 6.0, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-20067 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-20067?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-20067 have an EU (EUVD) identifier?: Yes. CVE-2025-20067 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-24439.
When was CVE-2025-20067 published?: CVE-2025-20067 was published on 2025-08-12 and last updated on 2026-06-17.

References

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01280.html

Other CWE-208 vulnerabilities

CVE-2023-41313 — Critical (CVSS 9.8): The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended…
CVE-2024-42512 — High (CVSS 8.6): Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass…
CVE-2025-53940 — High (CVSS 8.5): Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central…
CVE-2026-47784 — High (CVSS 8.1): In memcached before 1.6.42, password data for SASL password database authentication has a timing side channel because…
CVE-2026-47783 — High (CVSS 8.1): In memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a…
CVE-2026-42602 — High (CVSS 8.1): azureauthextension is the Azure Authenticator Extension. From 0.124.0 to 0.150.0, a server-side authentication bypass…

Browse all CWE-208 vulnerabilities →