Org.keycloak.protocol.oidc.grants: org.keycloak.services.managers: keycloak: server-side request forgery via oidc token endpoint manipulation
Noroxi assessment
Priority: Monitor (action score 12/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.32% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: org.keycloak:keycloak-services (Maven) 26.6.3, 26.4.13.
Low priority for now. Upgrade to org.keycloak:keycloak-services (Maven) 26.6.3, 26.4.13 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. An authenticated attacker can perform Server-Side Request Forgery (SSRF) by manipulating the `client_session_host` parameter during refresh token requests. This occurs when a Keycloak client is configured to use the `backchannel.logout.url` with the `application.session.host` placeholder. Successful exploitation allows the attacker to make HTTP requests from the Keycloak server’s network context, potentially probing internal networks or internal APIs, leading to information disclosure.
- Published
- Mar 26, 2026
- Updated
- Jun 26, 2026
- EPSS
- 0.3% · 24th percentile
- CWE
- CWE-918
Report tools
Action score
12
Monitor
Low priority for now.
- CVSS
- 12 / 40 · 3.1 / 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
- 3.1
- CNA · redhat
- 3.1
- agree
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
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 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 |
| redhat | jboss enterprise application platform | cpe:2.3:a:redhat:jboss_enterprise_application_platform |
| redhat | jboss enterprise application platform expansion pack | cpe:2.3:a:redhat:jboss_enterprise_application_platform_expansion_pack |
| redhat | single sign-on | cpe:2.3:a:redhat:single_sign-on |
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
- redhat jboss enterprise application platform8.0.0
- redhat jboss enterprise application platform expansion packall versions
- redhat single sign-on7.0
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 versionsaffected
- all versionsaffected
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
Red Hat Red Hat JBoss Enterprise Application Platform 8
- all versionsaffected
Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
- all versionsaffected
Red Hat Red Hat Single Sign-On 7
- all versionsaffected
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 | from 26.5.0 · before 26.6.3 | 26.6.3 |
| Maven | org.keycloak:keycloak-services | before 26.4.13 | 26.4.13 |
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-4628Mar 23, 2026 · Keycloak: org.keycloak.authorization: keycloak: unauthorized resource modification due to improper access control17Monitor
- ← EarlierCVE-2026-4633Mar 23, 2026 · Keycloak: keycloak: user enumeration via differential error messages14Monitor
- Later →CVE-2026-3121Mar 26, 2026 · Keycloak: org.keycloak/keycloak-services: keycloak: privilege escalation via manage-clients permission28Monitor
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.4.13 | Package registry (OSV) |
| 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.
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-43668 days apartKeycloak-services: blind server-side request forgery (ssrf) via http redirect handling in keycloak23Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-304721 days apartOrg.keycloak.broker.saml: keycloak saml broker: authentication bypass due to disabled saml client completing idp-initiated login35Monitor
- CVE-2026-26039 days apartKeycloak: keycloak: unauthorized authentication via disabled saml identity provider32Monitor
- CVE-2026-300921 days apartOrg.keycloak/keycloak-services: improper enforcement of disabled identity provider in identitybrokerservice (authentication bypass)32Monitor
- CVE-2026-1180091 days apartOrg.keycloak:keycloak-services: keycloak: authentication bypass via jwt algorithm confusion32Monitor
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.