CVE-2025-31356

MEDIUMPre-NVD 5.65.6
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Insufficient verification of data authenticity for some Intel(R) Trust Domain Extensions (Intel(R) TDX) within Ring 0: Hypervisor may allow an information disclosure. A system software adversary with a privileged user access combined with a high complexity attack may enable data exposure. This result may potentially occur via local access when attack requirements are present without any user interaction. The potential vulnerability may impact the confidentiality (high), integrity (low) and no effect on availability. Subsequent system impacts include reduced confidentiality (low), integrity (low), and no effect on availability.

CVSS v3
5.6
EG Score
5.6(low)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity56% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

INTEL-SA-01419

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

Vendor Advisories for CVE-2025-31356(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 03:23 UTCEG score recompute
  2. 2026-08-20 03:23 UTCGHSA enrichment
  3. 2026-08-19 05:35 UTCGHSA enrichment
  4. 2026-08-18 07:47 UTCGHSA enrichment
  5. 2026-08-17 09:59 UTCGHSA enrichment
  6. 2026-08-16 12:12 UTCGHSA enrichment
  7. 2026-08-15 14:25 UTCGHSA enrichment
  8. 2026-08-14 16:37 UTCGHSA enrichment
  9. 2026-08-13 18:49 UTCGHSA enrichment
  10. 2026-08-12 21:02 UTCGHSA enrichment
  11. 2026-08-12 14:27 UTCEG score recompute
  12. 2026-08-12 14:27 UTCGHSA enrichment
  13. 2026-08-12 14:02 UTCEG score recompute
  14. 2026-08-12 14:02 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 17:43 UTCEG score recompute
  17. 2026-08-11 16:46 UTCEG score recompute
  18. 2026-08-11 16:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-31356?
CVE-2025-31356 is a medium vulnerability published on August 11, 2026. Insufficient verification of data authenticity for some Intel(R) Trust Domain Extensions (Intel(R) TDX) within Ring 0: Hypervisor may allow an information disclosure. A system software adversary with a privileged user access combined with a high complexity attack may enable data exposure. This…
When was CVE-2025-31356 disclosed?
CVE-2025-31356 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-31356 actively exploited?
CVE-2025-31356 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.9% of all scored CVEs.
What is the CVSS score of CVE-2025-31356?
CVE-2025-31356 has a CVSS v3 base score of 5.6 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2025-31356?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-31356, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-31356

Explore →

Is Your Infrastructure Affected by CVE-2025-31356?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs