`CVE-2026-11800` Build of Keycloak

Affected software	Build of Keycloak
Severity	8.1 High CVSS 3.1 2 scores
Fixed in	`26.6.4`
Weakness	CWE-347
Published	25 Jun 2026
Updated	25 Oct 2026

Description

A flaw was found in Keycloak. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an attacker with valid client credentials to bypass signature verification. By forging an assertion, the attacker can create unauthorized access tokens. This enables the attacker to impersonate any federated user linked to the affected Identity Provider, leading to unauthorized access and potential privilege escalation.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. The 3 repositories below are public GitHub repositories with fewer than 5 stars.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment exploitation: none
Indexed PoC 3 indexed, none at 5+ stars
EPSS 0.26% chance in 30 days

3 of these are GitHub repositories with fewer than 5 stars. They are listed for reference and don't count toward the exploitation status above.

Index	Artifact	First seen
GitHub PoC	POC for CVE-2026-11800 - JWT algorithm confusion in Keycloak identity brokering: the IdP RSA public key DER bytes are accepted as an HMAC secret, minting tokens for federated users without any private key. Vulnerable 26.6.3 vs fixed 26.6.4, mitigation notes included.	2026-11-10
GitHub PoC	PoC for CVE-2026-11800: Keycloak JWT algorithm confusion auth bypass (HS256 assertion signed with the IdP public RSA key). Fixed in Keycloak 26.6.4.	2026-11-10
GitHub PoC	Offline differential model of Keycloak JWT grant HMAC algorithm confusion (CVE-2026-11800), educational	2026-11-09

Index

Artifact

Stars

First seen

GitHub PoC

POC for CVE-2026-11800 - JWT algorithm confusion in Keycloak identity brokering: the IdP RSA public key DER bytes are accepted as an HMAC secret, minting tokens for federated users without any private key. Vulnerable 26.6.3 vs fixed 26.6.4, mitigation notes included.

2026-11-10

GitHub PoC

PoC for CVE-2026-11800: Keycloak JWT algorithm confusion auth bypass (HS256 assertion signed with the IdP public RSA key). Fixed in Keycloak 26.6.4.

2026-11-10

GitHub PoC

Offline differential model of Keycloak JWT grant HMAC algorithm confusion (CVE-2026-11800), educational

2026-11-09

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: keycloak/keycloak #50374.

Protection none
Action unverified
Review automated Upstream data
Record active

Decided by	Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding	This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix	https://bugzilla.redhat.com/show_bug.cgi?id=2487006 : a Red Hat bug: the triage, which links onward to the fix

Decided by

Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

Finding

This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

Candidate fix

https://bugzilla.redhat.com/show_bug.cgi?id=2487006 : a Red Hat bug: the triage, which links onward to the fix

CVSS

8.1 HIGH v3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 8.1 HIGH CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N secalert@redhat.com Secondary published

CVSS 3.1 8.1 HIGH CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N redhat-SADP Secondary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	8.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`	secalert@redhat.com	Secondary	published
CVSS 3.1	8.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`	redhat-SADP	Secondary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

org.keycloak:keycloak-services 0 26.6.4 unbounded

Package	Introduced	Fixed	Last affected
`org.keycloak:keycloak-services`	0	`26.6.4`	unbounded

Products and versions

2 products, 2 version entries

Source	Vendor	Product	Scheme	Affected versions
osv	org.keycloak	keycloak-services	generic	＜ 26.6.4
nvd	redhat	build of keycloak	generic	≥ 26.6 and ＜ 26.6.4

Source

Vendor

Product

Scheme

Affected versions

osv

org.keycloak

keycloak-services

generic

＜ 26.6.4

nvd

redhat

build of keycloak

generic

≥ 26.6 and ＜ 26.6.4

References

URL	Tags
https://bugzilla.redhat.com/show_bug.cgi?id=2487006	bugzilla
https://github.com/keycloak/keycloak/security/advisories/GHSA-j97h-3f8r-mrjr	WEB
https://github.com/keycloak/keycloak/issues/50357	WEB
https://github.com/keycloak/keycloak/pull/50374	WEB
https://github.com/keycloak/keycloak/commit/6d61885f20ac59a2ff8b823fc9ed1f1ef1019951	WEB
https://github.com/keycloak/keycloak/commit/d343c7373dcc7bfeb9dc14de2309836299c81837	WEB
https://access.redhat.com/errata/RHSA-2026:30083	WEB
https://access.redhat.com/errata/RHSA-2026:30084	WEB
https://access.redhat.com/security/cve/CVE-2026-11800	WEB
https://github.com/keycloak/keycloak	PACKAGE

URL

Timeline

Published	2026-06-25	By the CVE Program.
NVD record modified	2026-10-25	NVD's own last-modified date for this record.

Published

2026-06-25

By the CVE Program.

NVD record modified

2026-10-25

NVD's own last-modified date for this record.

How VRT decided (17 of 24 rules ran)

17 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven matched In scope Maven packages: org.keycloak:keycloak-services

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint matched Mitigation candidate References include candidate fix URL (bugzilla tier): https://bugzilla.redhat.com/show_bug.cgi?id=2487006

18 open-source-maven skipped The affected package being open source on Maven, so the fix can be read

19 poc-derivable skipped An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit skipped Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match no match A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold no match Severity is HIGH — only MEDIUM/LOW are deprioritized

24 no-exploit-published decided it matched No exploit published No exploit code has been published, and an upstream fix path does exist, so the remediation half of the candidacy still holds.

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

redhat build_of_keycloak not tracked cpe:2.3:a:redhat:build_of_keycloak:*:*:*:*:*:*:*:*

NVD ↗ · CVE.org ↗