HIGH 7.4

CVE-2026-44946: SAML Assertion Replay Vulnerability in SUSE Rancher 2.14.0–2.14.2

Rancher's SAML authentication system has a replay vulnerability that allows attackers to reuse previously captured SAML assertions. SAML assertions are security tokens sent during login; normally, they should only work once. Because Rancher's Assertion Consumer Service (ACS) handler fails to enforce this one-time-use restriction, an attacker positioned on the network could intercept a valid SAML assertion and replay it multiple times to impersonate the original user. This is a man-in-the-middle risk that affects Rancher 2.14.0 through 2.14.2.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.4 HIGH · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Weaknesses (CWE)
CWE-294
Affected products
1 configuration(s)
Published / Modified
2026-06-30 / 2026-07-02

NVD description (verbatim)

A SAML authentication replay vulnerability in Rancher's Assertion Consumer Service (ACS) handler did not enforce one-time use of SAML assertion, potentially allowing person in the middle attacks against Rancher, affecting Rancher 2.14.0 before 2.14.3,

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-44946 is a SAML assertion replay vulnerability in Rancher's ACS endpoint. The vulnerability stems from inadequate validation of assertion freshness and consumption state. SAML assertions contain cryptographic signatures and timestamps; the one-time-use principle requires that once an assertion has been consumed in an authentication transaction, the same assertion cannot be accepted again, even if all signatures validate correctly. Rancher's ACS handler does not properly track or enforce this constraint, enabling an attacker with network visibility (such as a compromised network segment or rogue proxy) to capture an assertion and submit it again to establish a new authenticated session. The vulnerability requires the attacker to have network access to intercept or redirect SAML flows, placing it at the intersection of authentication bypass and replay attacks (CWE-294: Improper Validation of Specified Quantity in Input).

Business impact

Successful exploitation allows attackers to hijack user sessions without knowledge of passwords or multi-factor authentication secrets. In environments where SAML is federated across multiple applications, a single compromised assertion could be replayed against Rancher and potentially other integrated services. This directly undermines identity assurance and could lead to unauthorized access to infrastructure management functions within Rancher, cluster administration, and workload deployment. For organizations relying on Rancher for multi-tenant Kubernetes management, this creates privilege escalation and lateral movement risks.

Affected systems

SUSE Rancher versions 2.14.0, 2.14.1, and 2.14.2 are affected. The vulnerability is resolved in Rancher 2.14.3 and later. Organizations should verify their current Rancher version and check the official SUSE Rancher security advisory for definitive patch availability across all supported branches and distributions.

Exploitability

Exploitation requires network-level access to observe or intercept SAML authentication traffic—typically not achievable from the public internet unless the SAML endpoint is directly exposed or an attacker has compromised network infrastructure on the path between the client and Rancher. The vulnerability does not require user interaction and does not need elevated privileges to trigger. The CVSS score of 7.4 (HIGH) reflects high confidentiality and integrity impact but assumes an attacker can actively participate in network communications, placing the attack complexity at 'High.' This is not a trivial worm-like vector, but organizations with exposed Rancher instances or weakly segmented networks face meaningful risk.

Remediation

Upgrade SUSE Rancher to version 2.14.3 or later. Organizations on versions 2.14.0–2.14.2 should treat this as a priority patching target. Verify patch deployment by confirming Rancher version post-upgrade. Until patching is complete, network isolation and strict access control to the SAML ACS endpoint can reduce exposure. Consult the official SUSE Rancher security advisory for detailed upgrade paths and any version-specific considerations.

Patch guidance

Apply Rancher 2.14.3 or any subsequent release. If your organization is on an extended support branch, verify the corresponding patched version through the SUSE Rancher release notes. Test the upgrade in a non-production environment first to ensure no breaking changes or configuration conflicts. Pay particular attention to SAML configuration after patching to confirm IdP trust and assertion mappings remain intact. Document the patch application date and version for compliance and incident response records.

Detection guidance

Monitor SAML authentication logs for suspicious patterns: multiple successful authentications from the same assertion ID within a short time window, repeated login events from the same user with identical assertion timestamps, or authentication attempts with assertions bearing old creation times (timestamp validation). Network-based detection is challenging but possible via examining SAML POST request payloads for duplicate assertion IDs or by correlating authentication flows with session establishment times. Enable verbose logging on the SAML IdP and Rancher side to track assertion reuse. Host-based monitoring should alert on multiple concurrent session initiations from the same source IP bearing the same or very similar assertion identifiers.

Why prioritize this

Although not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog, the vulnerability carries a HIGH CVSS score (7.4) due to direct impact on authentication and authorization—core security functions. The threat is particularly acute for organizations that expose Rancher on partially trusted networks or rely on SAML as their primary authentication mechanism. Rancher's role as an infrastructure management platform means compromised sessions could affect large numbers of workloads and clusters. The three-patch sequence (2.14.0, 2.14.1, 2.14.2 all vulnerable) suggests the issue was not caught in initial release, increasing the likelihood of wide deployment. Prioritize patching for production Rancher instances, especially those in multi-tenant or internet-facing environments.

Risk score, explained

The CVSS 3.1 score of 7.4 reflects an attack vector that is network-accessible (AV:N) but requires the attacker to have an advantageous position to intercept or observe SAML traffic (AC:H). The confidentiality and integrity impacts are rated High (C:H, I:H) because successful replay leads to unauthorized session hijacking and potential lateral movement. Availability is not affected (A:N), as the attack does not disrupt service. The score is not in the CRITICAL range (9.0+) because exploitation is not trivially remote and unauthenticated; it requires either compromised network position or a misconfigured, publicly exposed SAML endpoint. However, it remains HIGH and warrants urgent remediation in production environments.

Frequently asked questions

Can an attacker exploit this vulnerability from the public internet without any special network access?

Not typically. The vulnerability requires the attacker to observe or intercept SAML authentication traffic, which usually means they must be on the same network segment, have compromised network infrastructure, or the SAML endpoint must be directly exposed on the internet. However, poorly segmented networks or inadvertent public exposure of Rancher instances do occur, so this risk should not be dismissed.

Does this vulnerability affect SAML providers (IdPs) like Okta or Azure AD, or only Rancher?

Only Rancher is vulnerable. The SAML provider validates and signs the assertion correctly; the flaw is in Rancher's ACS endpoint, which fails to enforce the one-time-use constraint after accepting a valid assertion. SAML providers themselves are not affected.

If we are using OIDC instead of SAML for authentication with Rancher, are we affected?

No. This vulnerability is specific to the SAML assertion handler. Organizations using OIDC (OpenID Connect) or other authentication methods are not impacted by CVE-2026-44946.

What should we do while we wait to schedule Rancher patching?

Immediately restrict network access to the Rancher SAML ACS endpoint to trusted IdP servers only. Implement strict network segmentation so that SAML traffic cannot be easily intercepted. Enable detailed logging on both the SAML IdP and Rancher to detect signs of assertion replay. Monitor for unusual session creation patterns. If your Rancher instance is internet-facing, consider temporarily moving it behind an additional authentication gateway or disabling SAML authentication until patching is complete. Plan patching as high-priority in your next maintenance window.

This analysis is provided for informational purposes only and is based on the CVE description and CVSS vector as of the publication date. Security vulnerabilities evolve, and patch availability may vary by platform, vendor support track, and regional distribution channels. Organizations should consult the official SUSE Rancher Security Advisory and your vendor for definitive guidance on affected versions, patch status, and upgrade procedures. Testing in non-production environments is strongly recommended before applying patches to critical systems. SEC.co does not warrant the accuracy or completeness of vulnerability data and assumes no liability for decisions made in reliance upon this analysis. Always verify findings against authoritative vendor sources and adapt remediation steps to your specific environment, compliance requirements, and risk tolerance. Source: NVD (public-domain), retrieved 2026-08-09. Analysis generated by SEC.co (claude-haiku-4-5).