CVE-2026-92855

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

GHSA-486h-gxch-8c4x ↗EUVD-2026-117606 ↗

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.
Red Hat Build of Keycloak
ETK-2026-3684Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 25msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+6h58m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Keycloak SAML identity-broker deployments that process holder-of-key assertions are affected. An attacker who obtains a victim's signed assertion may replay it to impersonate that user because proof of possession of the associated private key is not verified.

mitigation

Restrict access to affected SAML identity-broker flows and avoid holder-of-key assertion use where operationally feasible. Apply the vendor's update when available; the evidence does not identify a fixed version.

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
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 17:15Z
Δ 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-05 17:15Z
    ghsa: trigger signal, started the run
  2. 2026-11-05 17:15Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3684",
  "cve_id": "CVE-2026-92855",
  "display_id": "CVE-2026-92855",
  "ghsa_id": "GHSA-486h-gxch-8c4x",
  "euvd_id": "EUVD-2026-117606",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing holder-of-key validation in Keycloak SAML broker",
  "summary": "Keycloak SAML identity-broker deployments that process holder-of-key assertions are affected. An attacker who obtains a victim's signed assertion may replay it to impersonate that user because proof of possession of the associated private key is not verified.",
  "mitigation": "Restrict access to affected SAML identity-broker flows and avoid holder-of-key assertion use where operationally feasible. Apply the vendor's update when available; the evidence does not identify a fixed version.",
  "vendor": "Red Hat",
  "product": "Red Hat Build of Keycloak",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "keycloak/rhbk-openshift-rhel9",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "keycloak-services",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rhbk/keycloak-rhel9",
      "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": 15.8410268,
  "t0_at": "2026-11-05T17:15:07.565000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T17:15:07.565000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T17:15:07.565000+00:00",
      "url": "https://github.com/advisories/GHSA-486h-gxch-8c4x"
    }
  }
}

published 2026-11-05 23:57Z
last change 2026-11-06 08: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.