Live › vulnerability › CVE-2025-1397
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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 07:19 UTC. All times on this page are UTC.
Systems that accept JWT Bearer or SAML2 Bearer grants from identity providers that can be disabled, such as an OAuth or token service where an administrator turns off an IDP. Deployments that do not use these grant types, or that never disable identity providers, are unlikely to be exposed. The sources do not name the affected products or versions.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2025-1397")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.