CVE-2026-103314

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

  • High 7.4

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.

Key facts

Published
19 Oct 2026
Last changed
31 Oct 2026
Assigned by
redhat
EPSS
0.405% likely to be exploited in the next 30 days, higher than 35.424% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.4CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

What to do

  • 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, ConfCNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Advanced Cluster Security for Kubernetes 4.10
  • Default status: affected
  • 1793184257 up to but excluding * (unaffected)
Red HatRed Hat Advanced Cluster Security for Kubernetes 4.11
  • Default status: affected
  • 1792492060 up to but excluding * (unaffected)

Timeline

  1. 28 Sep 2026 Reported to Red Hat.
  2. 19 Oct 2026 Made public.
  3. 19 Oct 2026 Published

Weakness

References