CVE-2026-18570: Keycloak-services: keycloak-services: full-scope-disabled client policy validation bypass via omitted fullscopeallowed
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.30% (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 full-scope-disabled client-policy executor within the keycloak-services component. This component is responsible for enforcing security policies during client registration and configuration in Red Hat Build of Keycloak. The issue occurs because the executor only validates the fullScopeAllowed field when it is explicitly provided in a request. By omitting this field, a delegated user can bypass the policy, resulting in a client created with full scope access. This allows the client to obtain tokens with unauthorized role mappings.
- Published
- Aug 2, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-862
Report tools
Action score
21
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 itNoroxi 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 helpAffected 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.6
- 26.6.7-3 and laternot affected · rpm
- 26.6-20 and laternot affected · rpm
- 26.6-20 and laternot affected · rpm
Red Hat Red Hat build of Keycloak 26.6.7
- all versionsunknown
- all versionsunknown
- 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 recordsOther highest-scoring records for the same primary product.
- CVE-2026-16442Keycloak-services: keycloak-services: saml idp-initiated broker login bypasses link-only restriction39Monitor
- CVE-2026-16443Keycloak-services: keycloak-services: saml broker metadata import disables response signature validation36Monitor
- CVE-2026-15572Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-18208Jul 31, 2026 · Keycloak-services: keycloak-services: inactive out-of-audience token introspection leaks signed jwt claim26Monitor
- ← EarlierCVE-2026-18217Jul 31, 2026 · Keycloak-services: keycloak-services: saml http-redirect binding response preserves query string leading to parameter pollution18Monitor
- Later →CVE-2026-18571Aug 2, 2026 · Keycloak-services: keycloak-services: fgap v2 group assignment bypass during user creation28Monitor
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.
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 researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Paul Bottinelli (TrailBits in collaboration with OpenAI) for reporting this issue.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-182142 days apartKeycloak-services: keycloak-services: google external access-token exchange bypasses hosted-domain restriction32Monitor
- CVE-2026-185710 days apartKeycloak-services: keycloak-services: fgap v2 group assignment bypass during user creation28Monitor
- CVE-2026-185730 days apartKeycloak-services: keycloak-services: client access-type policy condition bypass during client update26Monitor
- CVE-2026-182082 days apartKeycloak-services: keycloak-services: inactive out-of-audience token introspection leaks signed jwt claim26Monitor
- CVE-2026-182014 days apartKeycloak-services: keycloak-services: generic identity-provider creation can bind brokers to organizations without manage-organizations22Monitor
- CVE-2026-182182 days apartKeycloak-services: keycloak-services: client not-before revocation ignored when realm not-before is older but nonzero21Monitor
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-862 · Missing AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.