Keycloak-services: keycloak-services: unauthenticated cpu denial of service via saml xml datetime and duration parsing
Red Hat Build of Keycloak and Red Hat Single Sign-On 7 servers that parse SAML XML with excessively long dateTime or duration values are affected. No 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: The checked facts do not describe a workaround. Until a fixed release is available, the sources give no specific mitigation to apply.
- 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 SAML XML processing component is affected, and an attacker can exhaust server CPU to cause a denial of service for all users. The attacker can do this remotely, without logging in, by sending specially crafted SAML requests containing excessively long dateTime or duration values.
Read the original description
A flaw was found in the SAML XML processing component of Keycloak, an open-source identity and access management solution. The issue occurs when the server parses XML documents containing excessively long dateTime or duration values. Because these strings are not properly validated before processing, the XML parser consumes excessive CPU time. An unauthenticated remote attacker can exploit this by sending specially crafted SAML requests to the server, leading to high CPU utilization and a denial of service for all users.
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: The checked facts do not describe a workaround. Until a fixed release is available, the sources give no specific mitigation to apply.
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-107123
Is CVE-2026-107123 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?
When the Keycloak server parses SAML XML documents that contain excessively long dateTime or duration values, it uses large amounts of CPU. This can cause high CPU utilization and a denial of service for all users.Source: access.redhat.com
Am I affected, and how do I check?
The checked facts name Red Hat Build of Keycloak and Red Hat Single Sign-On 7 but give no version ranges. The condition is a Keycloak server that parses SAML XML documents, so compare your installed Keycloak version with the version list in the Red Hat advisory.Source: access.redhat.com
How do I fix CVE-2026-107123?
The checked facts do not name a fixed release, so no upgrade target can be given from them. Check the Red Hat advisory for a fixed version and update to it once it is listed.Source: access.redhat.com
What if there's no patch?
The checked facts do not describe a workaround. Until a fixed release is available, the sources give no specific mitigation to apply.Source: access.redhat.com