← back to feed
CVE-2026-108267

CVE-2026-108267

validatedZero produced an exploit or a check.

GHSA-7jfw-53rm-phh2 ↗EUVD-2026-96017 ↗

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 go <= privasys-v0.3.0-go1.26.5
fixed in privasys-v0.5.1-go1.26.5
CWE-346 Origin Validation Error
ETK-2026-1239Zero'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
20mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+38h58magent stopped
0
+12h
+24h
+36h

description

Privasys Go releases before privasys-v0.5.1-go1.26.5 do not bind challenge-mode RA-TLS attestation to the active TLS session. An attacker who has obtained an enclave TLS private key may relay valid attestation and cause a relying party to treat the attacker's connection as an attested enclave connection.

mitigation

Upgrade Privasys Go to privasys-v0.5.1-go1.26.5 or later. Until upgraded, restrict access to enclave TLS private keys and avoid relying on challenge-mode RA-TLS attestation for connection identity.

fixed in privasys-v0.5.1-go1.26.5

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.12%1st percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 21:11Z
Δ 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:11Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-108267

this entry in the feed

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

{
  "etk_id": "ETK-2026-1239",
  "cve_id": "CVE-2026-108267",
  "display_id": "CVE-2026-108267",
  "ghsa_id": "GHSA-7jfw-53rm-phh2",
  "euvd_id": "EUVD-2026-96017",
  "status": "published",
  "anchor_state": "anchored",
  "title": "RA-TLS attestation relay in Privasys Go challenge mode",
  "summary": "Privasys Go releases before privasys-v0.5.1-go1.26.5 do not bind challenge-mode RA-TLS attestation to the active TLS session. An attacker who has obtained an enclave TLS private key may relay valid attestation and cause a relying party to treat the attacker's connection as an attested enclave connection.",
  "mitigation": "Upgrade Privasys Go to privasys-v0.5.1-go1.26.5 or later. Until upgraded, restrict access to enclave TLS private keys and avoid relying on challenge-mode RA-TLS attestation for connection identity.",
  "vendor": "Privasys",
  "product": "go",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= privasys-v0.3.0-go1.26.5"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "privasys-v0.5.1-go1.26.5"
      ],
      "package_name": "Privasys/go",
      "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.0012,
  "epss_percentile": 0.0159,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 19.65396805,
  "t0_at": "2026-10-09T21:11:33.186000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-11T12:09:15.910060+00:00",
      "days": 1.623411158101852,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T21:11:33.186000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-09T21:11:33.186000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T21:11:33.186000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108267"
    }
  }
}

published 2026-10-11 11:49Z
last change 2026-10-21 23:09Z

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.