CVE-2024-8698Public exploitNetwork attack vector

Privilege escalation via SAML signature scope confusion

Published Sep 19, 2024 · Updated Aug 4, 2026

Improper SAML signature verification in Keycloak before 25.0.5 allows remote authenticated users to impersonate privileged users. XMLSignatureUtil infers whether a signature covers the document or an assertion from its XML position instead of its Reference element, accepting an injected unsigned assertion alongside a valid signed assertion. Exploitation requires low-privileged access and a crafted SAML response; successful validation grants unauthorized access as the asserted privileged identity.

CVSS severity7.7
High
EPSS probability2.03%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper SAML signature verification in Keycloak before 25.0.5 allows remote authenticated users to impersonate privileged users. XMLSignatureUtil infers whether a signature covers the document or an assertion from its XML position instead of its Reference element, accepting an injected unsigned assertion alongside a valid signed assertion. Exploitation requires low-privileged access and a crafted SAML response; successful validation grants unauthorized access as the asserted privileged identity.

The record

CVE
CVE-2024-8698
Published
Sep 19, 2024
Updated
Aug 4, 2026
Vendor
Red Hat
Product
RHEL-8 based Middleware Containers
Classifications
CWE-347, T1606.002
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 19, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Red Hat · RHEL-8 based Middleware ContainersAffected versions are unavailable in this record.
Red Hat · Red Hat build of KeycloakAffected versions are unavailable in this record.
Red Hat · Red Hat Single Sign-On 7Affected versions are unavailable in this record.
Red Hat · Red Hat JBoss Enterprise Application Platform 8.0Affected versions are unavailable in this record.
Red Hat · Red Hat build of Keycloak 24Affected versions are unavailable in this record.
Red Hat · Red Hat build of Keycloak 22Affected versions are unavailable in this record.
Red Hat · Red Hat Single Sign-OnAffected versions are unavailable in this record.
Keycloak · Keycloakversion=0 <25.0.5

Published CVSS scores

7.7Red HatCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1606.002Forge Web Credentials: SAML Tokens

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo