CVE-2026-19729 Red Hat CVE debrief

Who should care

Keycloak administrators and security teams responsible for Keycloak deployments should assess their exposure and take mitigation steps to prevent potential information disclosure. This includes verifying and restricting keystore parameter inputs, monitoring for potential disclosure attempts, and reviewing compensating controls for exposed systems.

Why it matters

CVE-2026-19729 allows realm administrators to potentially expose sensitive system information by submitting arbitrary filesystem paths as keystore parameters. Keycloak administrators should assess their deployments, verify and restrict inputs, and monitor for potential disclosure attempts.

• Potential exposure of sensitive system information
• Need to verify and restrict keystore parameter inputs
• Monitoring for potential information disclosure attempts

Technical summary

The key provider component of the keycloak-services library has a flaw due to an incomplete fix for path probing, allowing realm administrators to submit arbitrary filesystem paths as keystore parameters. This can potentially expose sensitive system information by determining the existence and readability of files on the server. The vulnerability has a CVSS score of 4.9 and is classified as medium severity. Keycloak administrators should assess their deployments and take mitigation steps to prevent potential information disclosure.

Defensive priority

Medium priority for Keycloak administrators to assess and mitigate

Recommended defensive actions

• Assess Keycloak deployments for exposure to sensitive system information
• Verify and restrict keystore parameter inputs from realm administrators
• Monitor for potential information disclosure attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The issue is caused by an incomplete fix for path probing, allowing realm administrators to submit arbitrary filesystem paths as keystore parameters. This can be used to determine the existence and readability of files on the server, potentially exposing sensitive system information. Evidence is limited to the supplied CVE and NVD details, which indicate a medium severity vulnerability. Defenders should verify Keycloak deployments, restrict keystore parameter inputs, and monitor for potential information disclosure attempts.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.