NVD / CVE Program· CNA redhat

CVE-2026-9087: Keycloak: cross-session email verification proof not bound to upstream identity in first-broker-login

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: org.keycloak:keycloak-services (Maven) 26.6.3.

Low priority for now. Upgrade to org.keycloak:keycloak-services (Maven) 26.6.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A flaw was found in Keycloak. The cross-session verification proof is keyed only by (local userId, idpAlias) and is not bound to the upstream identity that was actually verified, so a second upstream account on the same IdP can consume it and get linked to the victim's local account.

HighCVSS 8.1 · v3.1—No exploit Fix available

GHSA-m6qj-3mpp-57v8

Published: May 20, 2026
Updated: Aug 3, 2026
EPSS: 0.3% · 23th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.1
CNA · redhat: 6.4; 1.7 point gap

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
redhat	build of keycloak	cpe:2.3:a:redhat:build_of_keycloak

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

redhat build of keycloakall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

Red Hat Red Hat build of Keycloak 26.4
- 26.4.13-1 and laternot affected · rpm
- 26.4-19 and laternot affected · rpm
- 26.4-19 and laternot affected · rpm
Red Hat Red Hat build of Keycloak 26.4.13
- all versionsunknown
Red Hat Red Hat build of Keycloak 26.6
- 26.6.3-3 and laternot affected · rpm
- 26.6-6 and laternot affected · rpm
- 26.6-6 and laternot affected · rpm
Red Hat Red Hat build of Keycloak 26.6.3
- all versionsunknown

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.keycloak:keycloak-services	before 26.6.3	26.6.3

Same product

redhat: all records

Other highest-scoring records for the same primary product.

CVE-2026-16442Keycloak-services: keycloak-services: saml idp-initiated broker login bypasses link-only restriction
39Monitor
CVE-2026-16443Keycloak-services: keycloak-services: saml broker metadata import disables response signature validation
36Monitor
CVE-2026-15572Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation
35Monitor

Published before and after this one in the same product

← EarlierCVE-2026-7507May 19, 2026 · Org.keycloak/keycloak-services: session fixation in oidc login flow that can lead to account takeover
30Monitor
← EarlierCVE-2026-7571May 19, 2026 · Keycloak: keycloak: access token disclosure and implicit flow bypass via forged client data
28Monitor
Later →CVE-2026-9704May 27, 2026 · Keycloak: keycloak: privilege escalation due to oversized subject_token jwt
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:org.keycloak:keycloak-services	26.6.3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Emilio Galle

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-909936 days apartKeycloak: group-admin escalation to realm-admin
30Monitor
CVE-2026-46301 days apartKeycloak: keycloak: unauthorized resource access and data modification via insecure direct object reference
27Monitor
CVE-2026-1705965 days apartKeycloak-services: keycloak-services: information disclosure via role-users endpoint bypasses per-user view filter
26Monitor
CVE-2026-1461444 days apartKeycloak-services: keycloak-services: fgap v2 client scope assignment bypass via clientresource
21Monitor
CVE-2026-379781 days apartKeycloak: org.keycloak.services: keycloak: information disclosure via evaluate-scopes admin api
19Monitor
CVE-2026-1610572 days apartKeycloak-services: keycloak-services: missing per-role authorization on rolecontainerresource composite endpoints
19Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

nvd-primary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

access.redhat.com/errata/RHSA-2026:25097

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records