CVE-2025-59363VulnerabilityPublished 14 Sep 2025Updated 15 Sep 2025

CVE-2025-59363: One Identity OneLogin · Incorrect Resource Transfer Between Spheres

Affects One Identity OneLoginSource CVE Database V5

Not known to be exploited · CVSS 7.7 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
One Identity OneLogin	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should prioritize upgrading OneLogin to version 2025.3.0 or later where the issue is resolved. Until patching is possible, organizations should restrict access to the GET Apps API v2 endpoint to trusted administrators only, implementing strict network segmentation and access control lists (ACLs). Monitoring and logging API access for unusual or unauthorized requests can help detect exploitation attempts early. Additionally, organizations should rotate OIDC client secrets for all applications managed through OneLogin to invalidate any potentially exposed credentials. Implementing multi-factor authentication (MFA) for administrative accounts accessing OneLogin can reduce the risk of privilege abuse. Reviewing and tightening API permissions and scopes to follow the principle of least privilege will also limit the impact of any leaked secrets. Finally, conducting regular security audits and penetration testing focused on IAM components can help identify and remediate similar issues proactively.

Description

In One Identity OneLogin before 2025.3.0, a request returns the OIDC client secret with GET Apps API v2 (even though this secret should only be returned when an App is first created),

Impact

For European organizations, this vulnerability poses a substantial risk to identity and access management (IAM) security. OneLogin is widely used across various sectors including finance, healthcare, government, and enterprise IT in Europe for centralized authentication and single sign-on (SSO) capabilities. Exposure of OIDC client secrets can enable attackers to bypass authentication controls, impersonate legitimate applications, and gain unauthorized access to sensitive data and internal systems. This could lead to data breaches, regulatory non-compliance (e.g., GDPR violations), and operational disruptions. Given the critical role of IAM in securing cloud and on-premises environments, exploitation could cascade into broader network compromises. The vulnerability’s remote exploitability without user interaction increases the attack surface, especially for organizations with externally accessible OneLogin APIs. The confidentiality breach could also undermine trust in federated identity setups and third-party integrations relying on OneLogin for authentication.

Summary

CVE-2025-59363 is a high-severity vulnerability affecting One Identity's OneLogin product versions prior to 2025.3.0. The issue stems from an incorrect resource transfer between security spheres, classified under CWE-669. Specifically, the vulnerability allows an attacker with at least low-level privileges (PR:L) to retrieve the OpenID Connect (OIDC) client secret via the GET Apps API v2 endpoint. Normally, the OIDC client secret should only be disclosed once during the initial app creation process to maintain confidentiality. However, due to this flaw, the secret is exposed on subsequent GET requests, increasing the risk of unauthorized access. The vulnerability is remotely exploitable over the network (AV:N) without requiring user interaction (UI:N), and it affects confidentiality (C:H) but does not impact integrity or availability. The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially compromised component. Although no known exploits are currently reported in the wild, the ease of exploitation combined with the sensitive nature of the leaked secret makes this a significant security concern. The OIDC client secret is critical for authentication flows and can be leveraged to impersonate applications or escalate privileges within the identity management environment, potentially leading to unauthorized access to protected resources and services integrated with OneLogin.

References

onelogin.service-now.com/support?id=kb_article&sys_id=b0aad1e11bd3ea109a47ec29b04bcb72&kb_category=a0d76d70db185340d5505eea4b96199f (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Sep 2025, 00:38 UTC

WeaknessesCWE-669

Technical details

References

Community reviews

Related threats