# CVE-2026-15614: IdP-initiated SAML sessions not reliably invalidated (replay)

> Attackers can replay IdP-initiated SAML sessions due to silent deletion failures, allowing unauthorized access within the session validity window.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-crqf-jj8w-c292

## What is CVE-2026-15614?

CVE-2026-15614 is a high-severity authentication bypass vulnerability in Logto, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Logto silently fails to delete IdP-initiated SAML sessions, enabling session replay and reuse within the session’s validity window.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2026-15614?


## How do I fix CVE-2026-15614?

No fix has been published for CVE-2026-15614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15614 being exploited?

There is no known exploitation of CVE-2026-15614 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15614 and fix it if it is affected.

What it is: CVE-2026-15614 is a high-severity authentication bypass vulnerability in Logto, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15614 in the wild and no public exploit code.

Affected product: Logto. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15614/ (Markdown: https://insights.sbomify.com/CVE-2026-15614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15614
- OSV: https://osv.dev/vulnerability/CVE-2026-15614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15614/
Summaries are generated and may contain mistakes; the official description above is the record.