Quick answers
- Is CVE-2026-103314 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103314 being exploited in the wild.
- How severe is CVE-2026-103314?
- High severity, with a CVSS score of 7.4, published 19 October 2026.
- Which products and versions are affected?
- Red Hat Advanced Cluster Security for Kubernetes.
- Is there a fix for CVE-2026-103314?
- No fixed version is recorded yet. Until an update is available, restrict network access to the Central SAML ACS endpoint to trusted identity providers and networks, and reduce SAML assertion lifetimes at the identity provider where possible. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-103314 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-103314?
- Check whether you run Red Hat Advanced Cluster Security for Kubernetes. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Until an update is available, restrict network access to the Central SAML ACS endpoint to trusted identity providers and networks, and reduce SAML assertion lifetimes at the identity provider where possible.
Technical details
The vulnerability is a replay attack in the SAML authentication flow (CWE-294). The Central ACS endpoint does not track or invalidate used SAML assertions or response identifiers, allowing an attacker who intercepts a valid signed SAML response to resubmit it before expiration and receive distinct authentication tokens. This requires SAML authentication to be enabled and the ACS endpoint to be reachable by the attacker; deployments using OIDC are protected.
Affected products
- Red Hat Advanced Cluster Security for Kubernetes
Timeline
- 2026-10-19: disclosed