Keycloak unable to restrict access to the admin console
CVE-2025-10939GHSA-vjr8-56p3-fmqq
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.keycloak:keycloak-quarkus-server 26.4.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.keycloak:keycloak-quarkus-server
- Affected
- < 26.4.4
- Fixed in
- 26.4.4
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-vjr8-56p3-fmqq lists affected ranges: Maven org.keycloak:keycloak-quarkus-server >=0 <26.4.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2025-10939: 0.41% estimated exploitation activity in the next 30 days; percentile 35.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
A flaw was found in Keycloak. The Keycloak guides recommend to not expose /admin path to the outside in case the installation is using a proxy. The issue occurs at least via ha-proxy, as it can be tricked to using relative/non-normalized paths to access the /admin application path relative to /realms which is expected to be exposed.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-vjr8-56p3-fmqq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-10939 Advisory: Keycloak unable to restrict access to the admin console IDs: CVE-2025-10939, GHSA-vjr8-56p3-fmqq Record: https://patchnext.com/advisories/cve-2025-10939 (revision 1, source checked 26 Oct 2026, 16:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 3.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.keycloak:keycloak-quarkus-server 26.4.4. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.keycloak:keycloak-quarkus-server: affected < 26.4.4; fixed in 26.4.4 ## Suggested inspection (read-only) - Maven org.keycloak:keycloak-quarkus-server: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.keycloak:keycloak-quarkus-server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-vjr8-56p3-fmqq (GitHub-reviewed advisory GHSA-vjr8-56p3-fmqq lists affected ranges: Maven org.keycloak:keycloak-quarkus-server >=0 <26.4.4) Commands are suggestions: review each one before running it.
Loading voting…