Keycloak-services: keycloak-services: unauthenticated persistent disk exhaustion via theme gzip cache
Red Hat Build of Keycloak and Red Hat Single Sign-On 7 are affected when theme caching is enabled and clients request gzip encoding. No vendor rating or fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: Disabling theme caching would remove the condition the facts describe as required for the bug. The checked facts do not list any official workaround.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 43/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The Keycloak identity and access management server is affected by a flaw in its theme resource endpoint, where theme names are not validated before being used for an on-disk gzip cache. Remotely, without logging in, an attacker can send many requests with fabricated theme names to exhaust disk space, and the damage persists across restarts and disrupts the service.
Read the original description
A flaw was found in the theme resource endpoint of Keycloak, an open-source identity and access management solution. The issue occurs because the server fails to validate theme names before using them as keys for an on-disk gzip cache. An unauthenticated attacker can exploit this by sending many requests with unique, fabricated theme names, leading to persistent disk space exhaustion that survives server restarts and causes service disruptions.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Shipped in major Linux distributions
- Severity7.5/10CVSS 7.5
- No patch5/5No patch listed yet
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 48 if advisories confirm default setups are exposed
What to do
Workaround: Disabling theme caching would remove the condition the facts describe as required for the bug. The checked facts do not list any official workaround.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- keycloak-services
Version range not reported
- rhbk/keycloak-rhel9
Version range not reported
- keycloak-services
Version range not reported
Evidence 2
- Report
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110932
Is CVE-2026-110932 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Requests for gzip-encoded themes can fill the server's disk through the theme cache. The space stays in use after a restart, which disrupts the service and can cause denial of service.Source: bugzilla.redhat.com, access.redhat.com
Am I affected, and how do I check?
The checked facts list Red Hat Build of Keycloak and Red Hat Single Sign-On 7, and the bug requires theme caching to be enabled and gzip encoding to be requested. To check a setup, review the theme caching setting in the server configuration and confirm the installed product version.Source: bugzilla.redhat.com, access.redhat.com
How do I fix CVE-2026-110932?
The checked facts do not name a fixed version, so no upgrade target can be given. Check the Red Hat advisory for a fixed release of the product in use.Source: bugzilla.redhat.com, access.redhat.com
What if there's no patch?
Disabling theme caching would remove the condition the facts describe as required for the bug. The checked facts do not list any official workaround.Source: bugzilla.redhat.com, access.redhat.com