Build Of KeycloakApplication · Redhat
CVE-2026-2603
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw was found in Keycloak. A remote attacker could bypass security controls by sending a valid SAML response from an external Identity Provider (IdP) to the Keycloak SAML endpoint for IdP-initiated broker logins. This allows the attacker to complete broker logins even when the SAML Identity Provider is disabled, leading to unauthorized authentication.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceKeycloak fails to validate whether a SAML Identity Provider is enabled before processing IdP-initiated broker login requests. An attacker can send a valid SAML response from a disabled external IdP to the Keycloak SAML endpoint, bypassing security controls and achieving unauthorized authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Build Of KeycloakApplication
>= 26.2, < 26.2.14>= 26.4, < 26.4.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Keycloak versionCheck the Keycloak server version by accessing the server info endpoint or reviewing server logs. The version is typically displayed in the admin console footer or via /health/ready endpoint.Affected if The installed version falls within the vulnerable range for this CVE (verify against official Keycloak security advisories).
-
List configured SAML Identity ProvidersIn the Keycloak admin console, navigate to Identity Providers section for each realm. Alternatively, use the admin REST API: GET /{realm}/identity-provider/instancesAffected if Any SAML Identity Provider is configured, regardless of enabled/disabled state.
-
Check SAML IdP enabled statusReview each SAML Identity Provider configuration and note its enabled/disabled status. Disabled IdPs may still be exploitable per this CVE.Affected if A SAML Identity Provider exists in disabled state but remains in the configuration.
-
Verify SAML broker login flowNavigate to Authentication > Flows in the admin console and confirm the 'Broker' flow or similar SAML broker login flow is active for the realm.Affected if The SAML broker login flow is enabled and bound to the authentication pipeline.
You are affected if running a vulnerable Keycloak version with any SAML Identity Provider configured (even if disabled) and the SAML broker login flow is active.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data26.2.1426.4.10
Apply vendor patches for CVE-2026-2603 when available; in the interim, consider disabling SAML broker functionality or implementing additional access controls on the SAML endpoint until the fix is deployed.
Fix this in Build Of Keycloak
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2603 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2603 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data