Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-3047 high CVSS 8.8

Vulnerability in org.keycloak.broker.saml (CVE-2026-3047)

Summary

Vulnerability in org.keycloak.broker.saml (CVE-2026-3047). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (SSO) session. This allows a remote attacker to gain unauthorized access to other enabled clients without re-authentication, effectively bypassing security restrictions.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-3047 has been found in org.keycloak.broker.saml.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.keycloak.broker.saml CVE-2026-3047" on the vendor's site.

CVE-2026-3047 (org.keycloak.broker.saml) — CWE-305 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-305) exists in org.keycloak.broker.saml.

📍 Affected scope

Check the vendor advisory for the affected versions of org.keycloak.broker.saml.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'org.keycloak.broker.saml' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'org.keycloak.broker.saml' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で org.keycloak.broker.saml を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.keycloak:keycloak-broker-saml
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.8.1.Final"}]}]
Bitnami keycloak
[{"type":"SEMVER","events":[{"introduced":"26.2.0"},{"fixed":"26.2.1"},{"introduced":"26.2.14"},{"fixed":"26.3.0"},{"introduced":"26.4.0"},{"fixed":"26.4.1"},{"introduced":"26.4.10"},{"fixed":"26.5.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details