high · 8.1 Patched

Keycloak vulnerable to authorization bypass via incorrect uri comparison

CVE-2026-9800 · GHSA-f5p5-6xmx-p252 · published 29 Oct 2026

How serious is it

  • Severity: high, CVSS score 8.1 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-9800?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • org.keycloak:keycloak-services (Maven) < 26.6.4
  • org.keycloak:keycloak-policy-enforcer (Maven) < 26.0.10

How to check

  1. Look for org.keycloak:keycloak-services in your lockfile and compare its version with the range above.
  2. Look for org.keycloak:keycloak-policy-enforcer in your lockfile and compare its version with the range above.
  3. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. On < 26.6.4: Upgrade org.keycloak:keycloak-services to 26.6.4 or later, commit the lockfile and redeploy.
  2. On < 26.0.10: Upgrade org.keycloak:keycloak-policy-enforcer to 26.0.10 or later, commit the lockfile and redeploy.
  3. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

### Description A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all authorization policies, including role, scope, and User-Managed Access (UMA) permission checks. By including the configured access-denied page path within a request URL, either as a path segment or a query parameter, an attacker can gain unauthorized access to protected resources.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database. Last updated 30 Oct 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities