← back to feed
CVE-2026-108268

CVE-2026-108268

validatedZero produced an exploit or a check.

GHSA-p5fp-g94g-g9m9 ↗EUVD-2026-96018 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Privasys enclave-os-virtual <= tdx-v0.2.35; <= tdx-gpu-v0.6.26-dev
fixed in tdx-v0.2.43, tdx-gpu-v0.6.27
CWE-346 Origin Validation Error
ETK-2026-1238Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.1cna vendorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
+1.6dTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+38h56magent stopped
0
+12h
+24h
+36h

description

Versions of enclave-os-virtual before tdx-v0.2.43 and tdx-gpu-v0.6.27 do not bind RA-TLS attestation evidence to the active TLS session. An attacker who obtains an enclave TLS private key may cause a relying party to accept an attacker-terminated connection as the attested enclave.

mitigation

Upgrade the applicable release track to tdx-v0.2.43 or later, or to tdx-gpu-v0.6.27 or later. Protect and rotate enclave TLS private keys as part of the update.

fixed in tdx-v0.2.43, tdx-gpu-v0.6.27

check
available
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.
0.13%2nd percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 21:13Z
Δ 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

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

  1. 2026-10-09 21:13Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-108268

this entry in the feed

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

{
  "etk_id": "ETK-2026-1238",
  "cve_id": "CVE-2026-108268",
  "display_id": "CVE-2026-108268",
  "ghsa_id": "GHSA-p5fp-g94g-g9m9",
  "euvd_id": "EUVD-2026-96018",
  "status": "published",
  "anchor_state": "anchored",
  "title": "TLS session binding omission in enclave-os-virtual RA-TLS",
  "summary": "Versions of enclave-os-virtual before tdx-v0.2.43 and tdx-gpu-v0.6.27 do not bind RA-TLS attestation evidence to the active TLS session. An attacker who obtains an enclave TLS private key may cause a relying party to accept an attacker-terminated connection as the attested enclave.",
  "mitigation": "Upgrade the applicable release track to tdx-v0.2.43 or later, or to tdx-gpu-v0.6.27 or later. Protect and rotate enclave TLS private keys as part of the update.",
  "vendor": "Privasys",
  "product": "enclave-os-virtual",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= tdx-v0.2.35",
        "<= tdx-gpu-v0.6.26-dev"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "tdx-v0.2.43",
        "tdx-gpu-v0.6.27"
      ],
      "package_name": "Privasys/enclave-os-virtual",
      "purl": null
    }
  ],
  "cwes": [
    346
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0013,
  "epss_percentile": 0.022,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 23.66236405,
  "t0_at": "2026-10-09T21:13:33.595000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-11T12:09:17.617308+00:00",
      "days": 1.6220372952314814,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T21:13:33.595000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-09T21:13:33.595000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T21:13:33.595000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108268"
    }
  }
}

published 2026-10-11 11:45Z
last change 2026-10-21 18:33Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.