HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.
  • CIGARPoint your coding agent at the right lines and cut its token bill by about a third.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.
  • Gauntlet benchmarkGuard tested with real coding agents: safe work runs, risky actions stop.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 93998 keycloak core keycloak core saml adapter does not
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard

Get HOL Guard for your computer

HOL Guard is a free desktop app that watches what coding agents such as Claude Code, Codex and Cursor run, read and install, and asks you before anything risky happens.

  • Download for macOS
  • Windows download
  • Linux download

Free. macOS 13+ on Apple silicon, Windows x64, Linux AppImage. Other ways to install

Runs on
macOS 13 or later on Apple silicon, Windows x64 and Linux x86_64.
Price
Free. Paid plans add Guard Cloud for teams. See pricing
Where your data stays
On your computer. Guard Cloud is optional.
Token savings
33% to 38% lower spend across three coding agents in our CIGAR benchmark.

HOL

HOL builds open infrastructure for AI agents: HOL Guard, a directory of AI plugins and MCP servers, an AI agent registry and the open HCS standards.

  • GitHub (opens in a new tab)
  • X (Twitter) (opens in a new tab)
  • YouTube (opens in a new tab)
  • Telegram (opens in a new tab)

HOL Guard

  • What is HOL Guard
  • Features
  • Cut coding agent token costs (CIGAR)
  • Install Guard
  • Download the desktop app
  • Pricing
  • Guard for teams
  • Compare Guard
  • Release notes

Guard for your AI tool

  • Guard for Claude Code
  • Guard for Codex
  • Guard for Cursor
  • Guard for GitHub Copilot CLI
  • Guard for OpenCode
  • Guard for Pi and Oh My Pi
  • Guard for Hermes
  • Guard for OpenClaw
  • All supported AI tools

Research and security

  • Gauntlet: Guard tested with real agents
  • CIGAR token benchmark
  • Research
  • AI security hub
  • Security advisories
  • Active CVEs in AI tools
  • AI agent security guides
  • Extensions and coverage

Plugins and MCP servers

  • Browse AI plugins
  • New plugin launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins

AI agent registry

  • Best AI agents
  • Best ERC-8004 agents
  • Best Virtuals agents
  • Best A2A agents
  • Best x402 payable agents
  • Submit an ERC-8004 contract
  • Feature your agent

Developers

  • Guard docs
  • Documentation index
  • Developer hub
  • Registry API reference
  • OpenAPI spec
  • Registry OpenAPI spec
  • Run in Postman (opens in a new tab)
  • HCS standards

Company

  • About HOL
  • Blog
  • Contribute to HOL
  • Guard contributors
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact

Copyright © 2026 HOL DAO LLC. All rights reserved.

  • Privacy
  • Terms of Service
Back to active CVEs
High · CVSS 7.4CVE-2026-93998

Keycloak-core: keycloak-core: saml adapter does not bind signed assertions to the configured identity provider issuerCVE-2026-93998

Answer in brief

CVE-2026-93998 records a High severity (CVSS 7.4) vulnerability in Keycloak-core: keycloak-core: saml adapter does not bind signed assertions to the configured identity provider issuer. The current sources do not mark it as known exploited. The current feed maps Red Hat/keycloak-core (generic), Red Hat/keycloak/rhbk-openshift-rhel9 (generic), Red Hat/keycloak/rhbk-rhel9-operator (generic), Red Hat/rhbk/keycloak-rhel9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Nov 5, 2026Updated Nov 6, 2026Source checked Nov 8, 2026First seen by HOL Nov 5, 2026Material review Nov 6, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.4
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Not reported

Why this deserves its current priority

CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/keycloak-core (generic), Red Hat/keycloak/rhbk-openshift-rhel9 (generic), Red Hat/keycloak/rhbk-rhel9-operator (generic), Red Hat/rhbk/keycloak-rhel9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Red Hat/keycloak-coregeneric*Not reported
Red Hat/keycloak/rhbk-openshift-rhel9generic*Not reported
Red Hat/keycloak/rhbk-rhel9-operatorgeneric*Not reported
Red Hat/rhbk/keycloak-rhel9generic*Not reported
Red Hat/rhbk/keycloak-rhel9-operatorgeneric*Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Red Hat/keycloak-core, Red Hat/keycloak/rhbk-openshift-rhel9, Red Hat/keycloak/rhbk-rhel9-operator.
  2. 2Review the reported fix. Source-reported workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce strict verification of the SAML assertion Issuer attribute against the configured identity provider entity ID in the Keycloak SAML adapter: upgrade to Red Hat build of Keycloak 26.4.17, 26.6.8 (or the corresponding fixed Red Hat builds), which verify that the Issuer attribute in the received SAML response and assertion strictly matches the configured identity provider entity ID, closing all 2 injection vectors (cross-tenant SAML assertion injection, shared-key sibling issuer assertion forging). Until patched, this is a concern on Applications secured using the Keycloak SAML adapter where signing keys are shared across multiple identity providers or tenants, so Ensure signing keys are strictly isolated per identity provider and never shared across multiple issuers or tenants. These controls limit blast radius and contain exploitation, but they do not fix the underlying missing SAML issuer validation defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high)

Evidence timeline and material changes

  1. Published upstream

    Nov 5, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Nov 6, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Nov 5, 2026

Sources and claim methodology

  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referencebugzilla.redhat.com
Upstream source description

A flaw was found in the SAML adapter component of Keycloak, which is used to secure applications with SAML-based authentication. The adapter fails to verify that the issuer of a signed SAML assertion matches the expected identity provider configured for the application. If multiple identity providers share the same trusted signing key, an attacker who controls one of those providers can create a validly signed assertion to log into the application as any user, potentially gaining full administrative control.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Hickory DNS 0.26.0-beta.1 before 0.26.2 Improper NSEC/NSEC3 Signature ValidationAlso CWE-347
  • Hickory DNS through 0.25.0-alpha.3 DNSSEC Validation Bypass via RRSIG Signer's NameAlso CWE-347

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-347
Source
CVE List V5
Source checked
Nov 8, 2026
References
6 linked sources
Open source record