Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
keycloak-saml-scanner — Detection-only triage for CVE-2026-117691 (CVSS 9.1): Keycloak SAML HTTP-Redirect binding signature bypass, fixed in 26.8.2 | Kitploit
도구/GitHubGitHub/foxcornlab/keycloak-saml-scanner
Defensive ToolsVulnerability ScannersIdentity ManagementVulnerability AnalysisConfiguration AuditingWeb SecurityAuthentication
GitHubfoxcornlab/keycloak-saml-scanner

keycloak-saml-scanner

Detection-only triage for CVE-2026-117691 (CVSS 9.1): Keycloak SAML HTTP-Redirect binding signature bypass, fixed in 26.8.2

저장소 보기
14일 전아직 검토되지 않음
공유
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

keycloak-saml-scanner

Local triage for CVE-2026-117691 (CVSS 9.1), a signature bypass in Keycloak's SAML HTTP-Redirect binding. Give it a Keycloak version you own, point it at an install directory, or point it at a Keycloak base URL, and it tells you whether that install is still open. It never sends a SAML message, never sends a crafted request, never logs in.

The flaw

CVE-2026-117691 is improper verification of cryptographic signature (CWE-347) in Keycloak's SAML HTTP-Redirect binding. Keycloak processes percent-encoded query parameter names (%53AMLResponse) while its signature verification only checks literal parameter names. An unauthenticated attacker supplies a crafted, unsigned SAML message, placed before the legitimately signed one in the request, and the server acts on the unsigned message instead. The result is full account takeover of federated users: log in as any user, get their roles and data, no credentials, no user interaction.

Only SAML is exposed. A realm that brokers SAML identity providers, or serves a SAML client over the HTTP-Redirect binding, is in scope. OIDC-only realms are not. Use --saml-usage no if you know no SAML is in use: a vulnerable version then grades NOT-EXPOSED instead of VULNERABLE, and the version grade is still shown.

The fix is Keycloak 26.8.2, released 5 November 2026. It is the only release carrying the fix, and it fixes 33 CVEs in one release, including the Brotli4j dependency flaw CVE-2026-111497 (graded separately by node2shell-inventory-scanner).

The traps: backports without the fix, and a dead line

SignalGradeWhy
26.8.2 or newerPATCHEDThe only release carrying the fix
26.8.0, 26.8.1VULNERABLEFix only in 26.8.2. 26.8.0 also carries the ; separator variant fixed in 26.8.1, so it has two bypasses in the same code path
26.7.xVULNERABLEEnd of life, no fix released at all
26.6.x up to 26.6.9VULNERABLEThe 26.6.9 backport does not include the fix. Taking the backport is not enough
26.4.x up to 26.4.18VULNERABLEThe 26.4.18 backport does not include the fix either
26.5.x and olderUNKNOWNThe advisory carries no affected-version data below 26.4, and no fix exists for those lines. Assume exposure if you use SAML redirect binding, and upgrade to 26.8.2. UNKNOWN is not clean
26.9.0-SNAPSHOT or any snapshotUNKNOWNA snapshot built before the fix commit is still vulnerable, so a snapshot cannot be graded as a release
26.4.2.redhat-00001 (RHBK)graded on the base versionRed Hat Build of Keycloak is affected too. Red Hat had no fixed RHBK build and no usable mitigation as of 6 November 2026

What it checks

  • A version you supply (--version 26.8.1): graded against the 26.8.2 fix
  • A version from a file (--version-file version.txt): reads the first line, or the version= line of a keycloak-version.properties file
  • An install directory (--local /opt/keycloak): detects the version from bin/kc.sh --version, from keycloak-version.properties inside the keycloak-common jar, from versioned jar filenames under lib/, or from the directory name. If the sources disagree it reports UNKNOWN with the conflict, never a silent pick
  • A live Keycloak you own (--url https://id.example.com): two plain unauthenticated GETs, the welcome page and the master-realm login page, and reads the version Keycloak itself prints in its theme resource URLs (resources/26.8.1/...). Verified against the Keycloak source: the welcome page builds that path from Version.RESOURCES_VERSION, which is the running version. It also reads the OIDC discovery document to confirm the target is Keycloak. It never logs in, never submits a form, never sends SAML
  • An offline inventory (--inventory-json keycloak.json): a JSON list of {label, version} or {label, path} entries, for a fleet of installs. Entries can carry their own "saml": "yes|no|unknown"
  • SAML usage (--saml-usage yes|no|unknown): no turns a vulnerable version into NOT-EXPOSED, because the flaw is not reachable without SAML. Default is unknown, which keeps the VULNERABLE grade and tells you to confirm
  • The CVE summary (--list): the flaw, the fix, and the backport situation

Usage

# vulnerable: one patch behind the fix
python3 keycloak_saml_scanner.py --version 26.8.1

# fixed
python3 keycloak_saml_scanner.py --version 26.8.2

# the backport trap: newest 26.6, still open
python3 keycloak_saml_scanner.py --version 26.6.9

# Red Hat build, graded on its upstream base version
python3 keycloak_saml_scanner.py --version 26.4.2.redhat-00001

# OIDC-only deployment: vulnerable code, not reachable
python3 keycloak_saml_scanner.py --version 26.8.1 --saml-usage no

# from an install directory (kc.sh, jars, or directory name)
python3 keycloak_saml_scanner.py --local /opt/keycloak

# from a live Keycloak you own (reads the version off its own pages)
python3 keycloak_saml_scanner.py --url https://id.example.com

# a fleet, from a file you own
python3 keycloak_saml_scanner.py --inventory-json keycloak.json

# machine-readable output
python3 keycloak_saml_scanner.py --version 26.8.1 --json

# the CVE summary
python3 keycloak_saml_scanner.py --list

Exit codes: 0 = nothing vulnerable found, 2 = vulnerable finding, 1 = scan error. UNKNOWN does not change the exit code, but it is not clean. An unparseable version, a snapshot build, or a version below 26.4 has not been cleared. It has simply not been graded.

Tests

python3 -m unittest discover -s tests -v

47 tests, all passing: patched and vulnerable grades across the 26.8, 26.7, 26.6 and 26.4 lines, the backport traps, UNKNOWN grades below 26.4 and for snapshots, RHBK suffix handling, the --saml-usage verdicts, version extraction from welcome and login page HTML, kc.sh / jar / directory-name detection including a source-disagreement case, and CLI exit codes, JSON output, inventory grading, and live probes against a mock Keycloak server.

Sources

  • Keycloak 26.8.2 release notes, keycloak.org, 5 November 2026: the fix, issue #54714, 33 CVEs in the release
  • Red Hat CVE-2026-117691 page: CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), the percent-encoding mechanism, no mitigation, reporter Mayssen Aidoudi (Think-it GmbH)
  • GHSA-c85j-3hq2-q6wj: published 5 November 2026, CVSS 9.1, no affected or patched version data
  • phasetwo.io, Keycloak 26.8.2: 33 CVEs and a Critical SAML Bypass, updated 6 November 2026: the ; separator variant fixed in 26.8.1, and the 26.6.8/26.6.9 and 26.4.17/26.4.18 backports lacking the fix, with 26.7 end of life
  • Keycloak source, WelcomeResource.java and Version.java (current main): the welcome page builds resourcesPath as resources/ + Version.RESOURCES_VERSION, and RESOURCES_VERSION is the running version lowercased, which is what --url reads

Two disagreements to note. First, the advisory says nothing about which versions are affected, so this tool grades 26.4 through 26.8.1 as vulnerable on the strength of the fix release and the backport analysis, and everything below 26.4 as UNKNOWN rather than guessing. Second, the Red Hat page carries an AI-generated mitigation block claiming fixed RHBK builds exist; the same page's own statement says Red Hat currently offers no mitigation meeting its criteria, so this tool follows the Red Hat statement and flags RHBK versions as having no confirmed fixed build as of 6 November 2026. phasetwo counts 33 fixes while 36 CVE IDs appear in the release notes; three are cited only as earlier issues the release repairs, so this tool says 33.

도구 다운로드

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 궁극의 OSINT 툴킷: 조사 그래프, 신뢰도 점수 산정, 별칭 패밀리, 지도, 타임라인 및 보고서. 49개 모듈, 400개 이상 사이트, API 키 불필요.

    1.1k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # GhostLock 원탭 실행 앱 (CVE-2026-43499)

    627
  • 3

    looking-glass

    anonghosty/looking-glass

    Shadowserver 보고서를 MongoDB로 수집하고 이를 대화형 지도, 분석, 발견 사항, 권고 및 경영진 대시보드로 재생하는 CSIRT 플랫폼입니다.

    413
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer는 오픈소스 권한 접근 관리(PAM) 플랫폼으로, DevOps 및 IT 팀이 웹 브라우저를 통해 SSH, RDP, Kubernetes, 데이터베이스 및 RemoteApp 엔드포인트에 주문형 보안 액세스를 제공합니다.

    350
  • 5

    ARTEX

    baarai/artex

    LLM 멀티 에이전트 자율 침투 테스트 플랫폼으로, 플래너/워커 에이전트, 자산 및 탐색 그래프, MITM 트래픽 기록, 취약점 재테스트 기능을 제공합니다.

    329
  • 6

    Aliens_eye

    arxhr007/aliens_eye

    웹 전반에서 7,700개 이상의 소셜 미디어 신원을 발견하고 매핑하는 AI 기반 OSINT 엔진

    283

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →