CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Keycloak SAML 1.1 AuthorityBinding parser loop, unauthenticated JVM termination (incomplete fix of CVE-2026-7307)

cve · CVE-2026-110931 single-source

Coverage
1
first 2026-11-08 → last 2026-11-08
Latest activity
2026-11-08
Keycloak 26.8.2 fixes a SAML signature bypass that logs an unauthenticated attacker in as any federated user
Peak priority
notable
1 notable
Targets
·
no sector or region stated
Sources cited
3
3 hosts

Action items (1)

Do-now tasks recorded on the entries about CVE-2026-110931, newest first. Check the date before acting on an older one.

  • Upgrade every Keycloak instance that brokers a SAML identity provider to 26.8.2, and every Red Hat build of Keycloak 26.6 to 26.6.9 (RHSA-2026:96040; container images RHSA-2026:96039), internet-reachable login endpoints first.
    2026-11-08CVE-2026-117691 +1

Defender insights

What each entry about CVE-2026-110931 tells a defender to do, newest first.

2026-11-08NOTABLEKeycloak 26.8.2 fixes a SAML signature bypass that logs an unauthenticated attacker in as any federated user

Exposure · detection

Story timeline

  1. 2026-11-08CVE-2026-117691, Keycloak SAML HTTP-Redirect signature bypass: a percent-encoded parameter name lets an unauthenticated attacker log in as any federated user; fixed in Keycloak 26.8.2
    trending-vulnerabilitiesKeycloak 26.8.2 fixes a SAML signature bypass that logs an unauthenticated attacker in as any federated user
ATT&CK techniques (3 across 3 tactics)

3 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application
  • Credential AccessForge Web Credentials: SAML Tokens
  • ImpactEndpoint Denial of Service: Application or System Exploitation

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-11-08/cve-2026-117691-keycloak-saml-http-redirect-signature-bypass · ATT&CK page ↗

Credential Access TA0006

T1606.002Forge Web Credentials: SAML Tokens×1

An adversary may forge SAML tokens with any permissions claims and lifetimes if they possess a valid SAML token-signing certificate. The default lifetime of a SAML token is one hour, but the validity period can be specified in the <code>NotOnOrAfter</code> value of the <code>conditions ...</code> element in a token. This value can be changed using the <code>AccessTokenLifetime</code> in a <code>LifetimeTokenPolicy</code>. Forged SAML tokens enable adversaries to authenticate across services that use SAML 2.0 as an SSO (single sign-on) mechanism.

Evidence: 2026-11-08/cve-2026-117691-keycloak-saml-http-redirect-signature-bypass · ATT&CK page ↗

Impact TA0040

T1499.004Endpoint Denial of Service: Application or System Exploitation×1

Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users. Some systems may automatically restart critical applications and services when crashes occur, but they can likely be re-exploited to cause a persistent denial of service (DoS) condition.

Evidence: 2026-11-08/cve-2026-117691-keycloak-saml-http-redirect-signature-bypass · ATT&CK page ↗

Entries about Keycloak SAML 1.1 AuthorityBinding parser loop, unauthenticated JVM termination (incomplete fix of CVE-2026-7307) (1)

2026-11-08 · view entry permalink →

NOTABLECVE-2026-117691 +1NATOA2

CVE-2026-117691, Keycloak SAML HTTP-Redirect signature bypass: a percent-encoded parameter name lets an unauthenticated attacker log in as any federated user; fixed in Keycloak 26.8.2

Keycloak 26.8.2, released on 2026-11-05, fixes CVE-2026-117691, a SAML redirect binding signature bypass via a percent-encoded parameter name (%53AMLResponse) that its release notes describe as broker login as any user (Keycloak, 2026-11-05). Red Hat, the CNA, explains that Keycloak's SAML HTTP-Redirect binding processes percent-encoded parameter names while the signature verification logic checks only literal ones, so an attacker can supply a crafted, unsigned SAML message that the server processes instead of a legitimately signed one; it scores the flaw CVSS 3.1 9.1 with no privileges or user interaction, rates it Important because it allows full account takeover of federated users, and says no available mitigation meets its criteria; it lists its build of Keycloak 26.6.9 packages as fixed by RHSA-2026:96040 and the 26.6 container images by RHSA-2026:96039, both released on 2026-11-07, and Red Hat Single Sign-On 7 as not affected (Red Hat, 2026-11-05). Its courtesy guidance describes the attack as a crafted request that places an encoded unsigned SAML parameter before a legitimately signed one, and suggests auditing and restricting account registration on external identity providers so attackers cannot capture legitimately signed redirect-binding messages (Red Hat, 2026-11-05).

The release fixes further issues tagged with CVE identifiers, among them an unauthenticated single-request JVM termination through a SAML 1.1 AuthorityBinding parser loop, labelled an incomplete fix of an earlier flaw (CVE-2026-110931), unauthenticated CPU and worker-pool exhaustion through the SAML 1.1 KeyInfo parser that needs a restart (CVE-2026-107602), unverified identity-provider email auto-linking that enables account takeover (CVE-2026-97175), an account takeover through an authentication race (CVE-2026-103112) and a SAML broker that accepts holder-of-key assertions without proof of key possession (CVE-2026-92855) (Keycloak, 2026-11-05). The release also fixes CVE-2026-111497, the out-of-bounds write in its bundled Brotli decoder (Keycloak, 2026-11-05), which CISA lists as exploited (CISA, 2026-10-27). No source reports exploitation of the SAML flaws or a public proof of concept; CISA's listing concerns the Brotli decoder.

SAML redirect binding signature bypass via percent-encoded parameter name (%53AMLResponse)

Keycloak project (release notes 26.8.2) 2026-11-05

The issue occurs because the server processes percent-encoded parameter names (like %53AMLResponse) while the signature verification logic only checks literal parameter names.

it allows for full account takeover of federated users

Red Hat Product Security (CVE page) 2026-11-05

Builds on: Node2Shell Brotli flaw is now on CISA KEV, with exploit traffic seen against Node.js 24.22.0… · Brotli flaw hits Desigo CC, Industrial Edge and Mitel; Cisco lists Duo; Mitel and Common…

vulnerability08 Nov 14:12Zsingle-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • access.redhat.com1 (33%)
  • cisa.gov1 (33%)
  • keycloak.org1 (33%)