CVE-2025-52925: OneLogin Active Directory Connector · Resource Leak
Affects OneLogin Active Directory ConnectorSource CVE Database V5
Not known to be exploited · CVSS 5.0 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% 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:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jul 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OneLogin Active Directory Connector | Affected
| Fixed in– |
AI-suggested
European organizations should prioritize upgrading the OneLogin Active Directory Connector to version 6.1.5 or later once the patch is officially released. Until then, organizations should implement compensating controls such as restricting network access to the Active Directory Connector to trusted management networks and enforcing strict privilege management to limit who can interact with the connector. Monitoring and logging authentication token usage and access patterns can help detect anomalous activities indicative of exploitation attempts. Additionally, organizations should review and tighten encryption configurations and key management practices related to the DirectoryToken. Employing network segmentation to isolate identity management components and enforcing multi-factor authentication (MFA) for administrative access can further reduce risk. Regularly auditing and validating the integrity of identity connectors and tokens will help identify potential leaks early. Finally, organizations should prepare incident response plans specific to identity token compromise scenarios to minimize impact if exploitation occurs.
Description
In One Identity OneLogin Active Directory Connector before 6.1.5, encryption of the DirectoryToken was mishandled, aka ST-812.