CVE-2026-57890

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qmww-m9ph-47gp ↗EUVD-2026-121676 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Intel(R) TDX Migration Trust Domain (MigTD) See references
CWE-460 Improper Cleanup on Thrown Exception
ETK-2026-4082Zero's internal tracking ID, independent of the CVE number., permanent identifier
11h 48msince last run
46mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h11m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

The Ring 0 SPDM responder in Intel TDX Migration Trust Domain (MigTD) can retain information improperly when an exception is handled. An unauthenticated network attacker who can reach the responder may be able to obtain exposed data without user interaction.

mitigation

Restrict network access to the MigTD SPDM responder to trusted systems and networks until an update is available. Apply Intel's corrected release when it is published.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
46m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 17:46Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-10 17:46Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-57890

{
  "etk_id": "ETK-2026-4082",
  "cve_id": "CVE-2026-57890",
  "display_id": "CVE-2026-57890",
  "ghsa_id": "GHSA-qmww-m9ph-47gp",
  "euvd_id": "EUVD-2026-121676",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Exception cleanup information disclosure in MigTD SPDM responder",
  "summary": "The Ring 0 SPDM responder in Intel TDX Migration Trust Domain (MigTD) can retain information improperly when an exception is handled. An unauthenticated network attacker who can reach the responder may be able to obtain exposed data without user interaction.",
  "mitigation": "Restrict network access to the MigTD SPDM responder to trusted systems and networks until an update is available. Apply Intel's corrected release when it is published.",
  "vendor": null,
  "product": "Intel(R) TDX Migration Trust Domain (MigTD)",
  "affected": [
    {
      "affected_notes": [
        "See references"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Intel(R) TDX Migration Trust Domain (MigTD)",
      "purl": null
    }
  ],
  "cwes": [
    460
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 45.58029908333334,
  "t0_at": "2026-11-10T17:46:42.831000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T17:46:42.831000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T17:46:42.831000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-57890"
    }
  }
}

published 2026-11-10 18:12Z
last change 2026-11-11 05:12Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.