NVD / CVE Program· CNA redhat

CVE-2026-14614: Keycloak-services: keycloak-services: fgap v2 client scope assignment bypass via clientresource

MediumCVSS 5.4 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 21/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. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

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 the ClientResource component of Keycloak's admin services when Fine-Grained Admin Permissions (FGAP) v2 is enabled. This issue allows a delegated administrator, who should only have limited control over specific clients, to attach or remove hidden client scopes that they are not authorized to see or manage. As a result, an attacker could inject unauthorized data or permissions into the security tokens issued to end-users, potentially tricking other applications into granting higher levels of access than intended.

Broken access control (IDOR)

Published: Jul 3, 2026
Updated: Aug 11, 2026
EPSS: 0.3% · 24th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · redhat: 5.4; NVD has not scored this yet; the score shown is the CNA’s.

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
No fixed version yet

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

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 keycloak26.4 and later · before 26.4.14
redhat build of keycloak26.6 and later · before 26.6.5

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
- all versionsunknown
- all versionsunknown
Red Hat Red Hat build of Keycloak 26.4
- 26.4.14-1 and laternot affected · rpm
- 26.4-22 and laternot affected · rpm
- 26.4-22 and laternot affected · rpm
Red Hat Red Hat build of Keycloak 26.4.14
- all versionsunknown
Red Hat Red Hat build of Keycloak 26.6
- 26.6.5-1 and laternot affected · rpm
- 26.6-11 and laternot affected · rpm
- 26.6-11 and laternot affected · rpm
Red Hat Red Hat build of Keycloak 26.6.5
- all versionsunknown
Red Hat Red Hat Data Grid 8
- all versionsunknown
Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
- all versionsunknown
Red Hat Red Hat Single Sign-On 7
- all versionsunknown

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-4629Jun 30, 2026 · Keycloak: keycloak: privilege escalation through hardcoded role mapper injection
26Monitor
← EarlierCVE-2026-14613Jul 3, 2026 · Keycloak-services: keycloak-services: keycloak: fgap v2 role groups endpoint discloses hidden group metadata without group view permission
19Monitor
Later →CVE-2026-14615Jul 3, 2026 · Keycloak-services: keycloak: fgap v2 parent group children endpoint bypasses per-child view permission filter
10Monitor

Remediation

Which version to upgrade to

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

No fix version is recorded for this entry. Check the references for vendor advisories.

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.

No history yet (it accumulates with the daily EPSS job).

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.

yd1ng

Variant candidates

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

CVE-2026-908744 days apartKeycloak: cross-session email verification proof not bound to upstream identity in first-broker-login
32Monitor
CVE-2026-90998 days apartKeycloak: group-admin escalation to realm-admin
30Monitor
CVE-2026-463045 days apartKeycloak: keycloak: unauthorized resource access and data modification via insecure direct object reference
27Monitor
CVE-2026-1705921 days apartKeycloak-services: keycloak-services: information disclosure via role-users endpoint bypasses per-user view filter
26Monitor
CVE-2026-3797945 days apartKeycloak: keycloak: information disclosure via oidc token introspection endpoint audience bypass
26Monitor
CVE-2026-1610528 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.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

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

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

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

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

nvd-secondary

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

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

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

Show all references (5 more)

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

All records