8000 Enforce at least one bearer subject confirmation method and also fail for unsupported methods by pedroigor · Pull Request #55013 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Enforce at least one bearer subject confirmation method and also fail for unsupported methods - #55013

Open
pedroigor wants to merge 1 commit into
keycloak:mainfrom
pedroigor:cve-1027
Open

pedroigor wants to merge 1 commit into
keycloak:mainfrom
pedroigor:cve-1027

Conversation

@pedroigor
Copy link
Copy Markdown
Contributor

Closes #54711

… for unsupported methods

Closes keycloak#54711

Signed-off-by: Pedro Igor <pigor.craveiro@gmail.com>
@pedroigor
pedroigor requested a review from a team as a code owner November 10, 2026 18:27
Copilot AI balanced review requested due to automatic review settings November 10, 2026 18:27
Copilot AI left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The documentation incorrectly implies that unsupported subject-confirmation methods cause login failure even when a valid bearer confirmation is present.

1 open issue
What changed in this PR

This PR tightens SAML identity-broker validation to require a valid bearer subject confirmation, preventing holder-of-key-only assertions from being accepted without proof of key possession.

Changes:

  • Reject assertions without a bearer confirmation while preserving acceptance of mixed-method assertions with a valid bearer confirmation.
  • Add regression tests and helpers for unsupported methods and expired bearer data.
  • Document the bearer-confirmation requirement in administrator and upgrade guides.
File Description
tests/​base/​src/​test/​java/​org/​keycloak/​tests/​saml/​SamlResponseDocument.java Adds helpers to modify subject confirmations and expire their data.
tests/​base/​src/​test/​java/​org/​keycloak/​tests/​broker/​saml/​KcSamlBrokerTest.java Tests unsupported-only and mixed-method assertions.
services/​src/​main/​java/​org/​keycloak/​broker/​saml/​SAMLEndpoint.java Rejects assertions with no bearer confirmation.
docs/​documentation/​upgrading/​topics/​changes/​changes-27_0_0.adoc Adds an upgrade note about unsupported confirmation methods.
docs/​documentation/​server_admin/​topics/​identity-broker/​saml.adoc Documents subject-confirmation support for SAML brokering.

Review effort: Balanced

{project_name} accepts the assertion only if a bearer confirmation is present and contains a `<SubjectConfirmationData>` element that validates, including the recipient, the `InResponseTo` value, and the validity window.

{project_name} does not support a subject confirmation method other than `bearer`.
Any other unsupported method is rejected and the login fails.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CVE-2026-92855] Keycloak SAML Broker Accepts Holder-of-Key Assertions Without Proof of Key Possession

2 participants

0