cve.bz

CVE-2026-61377

6.8 mediumEPSS 0.1%

Medium (6.8). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Sensitive information uncleared in resource before release for reuse in the MigTD for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an information disclosure. System software adversary with a privileged user combined with a high complexity attack may enable data exposure. This result may potentially occur via local 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 (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (none) and availability (none) impacts.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-226 Sensitive Information in Resource Not Removed Before Reuse
Published
Modified
Assigned by
intel (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-61377 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61377?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61377?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61377 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-61377

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-61377](https://cve.bz/cve/badge/CVE-2026-61377.svg)](https://cve.bz/cve/CVE-2026-61377)

HTML:

<a href="https://cve.bz/cve/CVE-2026-61377"><img src="https://cve.bz/cve/badge/CVE-2026-61377.svg" alt="CVE-2026-61377"></a>

Attack patterns (CAPEC)

  • CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON