CVE-2026-103314

Stackrox: stackrox: saml response replay allows multiple central authentication tokens

Published Oct 19, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
Description
A flaw was found in Red Hat Advanced Cluster Security for Kubernetes (RHACS). The Central SAML authentication ACS endpoint does not retain used SAML assertion or response identifiers to prevent replay. An attacker who obtains a valid, unexpired signed SAML response can submit it multiple times and receive distinct Central authentication tokens for the mapped identity.

Remediation

Vendor Workaround

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. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce replay tracking on the Central SAML Assertion Consumer Service endpoint to record and reject previously consumed assertion and response identifiers: upgrade to RHACS 4.11.6 (or the fixed Advanced Cluster Security/Rhacs Main Rhel builds), which record and reject previously consumed SAML response and assertion identifiers at the ACS endpoint, closing all 2 injection vectors (SAML response replay, SAML assertion identifier reuse). Until patched, this is only a concern on RHACS Central deployments on Linux with SAML authentication enabled and a reachable ACS endpoint — Deployments that do not use SAML authentication or rely on OIDC ID-token logins are unaffected — so Restrict network access to the Central SAML ACS endpoint to trusted identity providers and networks, and reduce SAML assertion lifetimes at the identity provider. As a compensating measure, Configure host-based firewall rules using firewalld or nftables to restrict reachability to the Central SAML ACS endpoint to authorized identity providers and trusted client subnets and Apply network segmentation via VLANs or subnets to isolate the network path to RHACS Central and restrict reachability to the SAML ACS endpoint. These controls limit blast radius and contain exploitation, but they do not fix the underlying missing SAML replay protection defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-202 Host-Based Firewall (firewalld/nftables) (medium)

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:/a:redhat:advanced_cluster_security:4 cpe:/a:redhat:advanced_cluster_security:4.10::el8
References
Type Values Removed Values Added
CPEs cpe:/a:redhat:advanced_cluster_security:4.11::el9
References
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description A flaw was found in Red Hat Advanced Cluster Security for Kubernetes (RHACS). The Central SAML authentication ACS endpoint does not retain used SAML assertion or response identifiers to prevent replay. An attacker who obtains a valid, unexpired signed SAML response can submit it multiple times and receive distinct Central authentication tokens for the mapped identity.
Title Stackrox: stackrox: saml response replay allows multiple central authentication tokens
First Time appeared Redhat
Redhat advanced Cluster Security
Weaknesses CWE-294
CPEs cpe:/a:redhat:advanced_cluster_security:4
Vendors & Products Redhat
Redhat advanced Cluster Security
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Oct 31, 2026, 10:00 AM
Reserved
Sep 30, 2026, 11:57 AM
Status
Awaiting Analysis
Published
Oct 19, 2026, 1:16 PM
Modified
Oct 31, 2026, 10:16 AM
Severity
Important
Public date
Oct 19, 2026, 10:00 AM