---
id: "CVE-2025-1397"
kind: "vulnerability"
aliases: ["CVE-2025-1397"]
title: "Identity provider: disabled IDP still issues access tokens via JWT or SAML bearer"
severity: "medium"
cvss: 4.8
epss: null
exploited: false
status: "open"
category: "vendor"
products: []
ecosystems: []
tags: ["identity-provider", "jwt", "oauth", "saml", "vendor"]
not_affected_if: ["grant-types-unused"]
published_at: "2026-11-03T07:17:19+00:00"
first_seen_at: "2026-11-03T07:19:16+00:00"
updated_at: "2026-11-03T07:21:11+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1397", "first_seen_at": "2026-11-03T07:19:16+00:00"}]
---

# Identity provider: disabled IDP still issues access tokens via JWT or SAML bearer

When a token is requested with the JWT Bearer or SAML2 Bearer grant types, the system does not check whether the identity provider is disabled before issuing access tokens. An attacker can obtain access tokens through a disabled identity provider and reach resources that should be blocked.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-11-03T07:19:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-1397

## From the sources

When utilizing JWT Bearer or SAML2 Bearer grant types, the system fails to validate the status of the Identity Provider (IDP) before issuing access tokens. This oversight permits tokens to be generated even when the associated IDP has been disabled.

A malicious actor could leverage this vulnerability to obtain access tokens by targeting a disabled IDP. This could enable them to bypass intended security controls and potentially access protected resources that should be inaccessible due to the IDP's disabled state.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_