CVE-2026-0976: Org.keycloak/keycloak-quarkus-server: keycloak: proxy bypass due to improper handling of matrix parameters in url paths
A flaw was found in Keycloak. This improper input validation vulnerability occurs because Keycloak accepts RFC-compliant matrix parameters in URL path segments, while common reverse proxy configurations may ignore or mishandle them. A remote attacker can craft requests to mask path segments, potentially bypassing proxy-level path filtering. This could expose administrative or sensitive endpoints that operators believe are not externally reachable.
Security readout for executives and security teams
Plain-English summary
Keycloak may accept URL path syntax that some reverse proxies mishandle. An attacker could disguise path segments and bypass proxy rules meant to block administrative or sensitive paths. The published severity is low because exploitation depends on specific proxy configurations and only limited confidentiality impact is described.
Executive priority
Treat as a configuration-sensitive low-severity issue. Prioritize review for internet-facing Keycloak deployments and environments relying on reverse proxy path rules to protect admin interfaces.
Technical view
CVE-2026-0976 is an improper input validation issue in keycloak-quarkus-server involving RFC-compliant matrix parameters in URL path segments. If a reverse proxy ignores or normalizes these differently than Keycloak, proxy-level path filtering may be bypassed, potentially exposing endpoints operators intended to keep internal.
Likely exposure
Organizations using affected Red Hat Keycloak-related packages behind reverse proxies with path-based access controls are the likely exposure group. Risk is higher where administrative or sensitive Keycloak paths rely on proxy filtering rather than network isolation and application authorization.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates network access, no privileges, no user interaction, high attack complexity, and limited confidentiality impact.
Researcher notes
Evidence is limited to the CVE description, Red Hat references, affected package names, and CVSS data. No affected version ranges, fixed versions, patches, or exploitation reports are provided in the source bundle.
Mitigation direction
Check Red Hat guidance for affected package status, errata, and supported fixes.
Review reverse proxy rules for path filtering around Keycloak administrative or sensitive endpoints.
Avoid relying only on proxy path filters to protect Keycloak admin endpoints.
Use network restrictions and strong application-level controls for administrative access.
Confirm proxy and backend handle matrix parameters consistently.
Validation and detection
Inventory Red Hat Build of Keycloak and listed JBoss EAP packages using keycloak-quarkus-server components.
Identify deployments where Keycloak is reachable through a reverse proxy.
Review proxy configurations for path-based allow or deny rules protecting sensitive Keycloak paths.
Test in a controlled environment whether matrix-parameter paths are normalized consistently.
Check Red Hat CVE and Bugzilla pages for updated affected versions and fixes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.