ETK-2026-2560Zero's internal tracking ID, independent of the CVE number.

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

GHSA-67m7-gf4w-hw23 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other:h2o commits up to d90ff82
fixed in commits ae55300 and above
ETK-2026-2560Zero's internal tracking ID, independent of the CVE number., no cve assigned
4h 09msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −38h27mwaiting for further signals−4h09m
−36h
−24h
−12h
0

description

H2O reverse proxies using TLS 1.3 may accept an HTTPS upstream certificate without confirming that its name matches the configured upstream. A network-positioned attacker with a certificate trusted for a different hostname could impersonate that upstream and inspect or modify proxied traffic. The issue applies when proxy.ssl.verify-peer: ON is enabled and TLS 1.3 is negotiated.

mitigation

Upgrade h2o to commits ae55300 and above or later.

fixed in commits ae55300 and above

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
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-23 08:48Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2560

{
  "etk_id": "ETK-2026-2560",
  "cve_id": null,
  "display_id": "ETK-2026-2560",
  "ghsa_id": "GHSA-67m7-gf4w-hw23",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "TLS 1.3 upstream hostname verification bypass in H2O",
  "summary": "H2O reverse proxies using TLS 1.3 may accept an HTTPS upstream certificate without confirming that its name matches the configured upstream. A network-positioned attacker with a certificate trusted for a different hostname could impersonate that upstream and inspect or modify proxied traffic. The issue applies when `proxy.ssl.verify-peer: ON` is enabled and TLS 1.3 is negotiated.",
  "mitigation": "Upgrade h2o to commits ae55300 and above or later.",
  "vendor": "other",
  "product": "other:h2o",
  "affected": [
    {
      "affected_notes": [
        "commits up to d90ff82"
      ],
      "affected_ranges": [],
      "ecosystem": "other",
      "fixed_versions": [
        "commits ae55300 and above"
      ],
      "package_name": "h2o",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.704363683333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-23T08:48:26+00:00",
      "days": -1.6019774476041666,
      "is_lower_bound": true,
      "measured_at": "2026-10-24T23:15:16.890846+00:00",
      "url": "https://github.com/h2o/h2o/security/advisories/GHSA-67m7-gf4w-hw23"
    }
  }
}

published 2026-10-24 18:57Z
last change 2026-10-24 23:06Z

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.