CVE-2025-34064: One Identity OneLogin Active Directory Connector (ADC) · Resource Exposure
Affects One Identity OneLogin Active Directory Connector (ADC)Source CVE Database V5
Not known to be exploited · CVSS 9.0 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 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 |
|---|---|---|
| One Identity OneLogin Active Directory Connector (ADC) | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should immediately verify whether their OneLogin ADC deployments are affected by checking the version and configuration. Since the vulnerability involves a hardcoded S3 bucket without ownership validation, organizations should: 1) Coordinate with One Identity to obtain and apply any available patches or updates that address this misconfiguration. 2) Audit and monitor S3 bucket policies and ownership to ensure no unauthorized buckets exist with names matching the hardcoded bucket. 3) Implement strict IAM policies and logging controls on AWS accounts to detect and prevent unauthorized bucket creation or access. 4) Temporarily disable or restrict the ADC's logging functionality to the hardcoded bucket until a secure configuration is confirmed. 5) Conduct thorough reviews of logs and access tokens for signs of compromise or unauthorized access. 6) Employ network segmentation and zero-trust principles to limit the impact of potential token leakage. 7) Engage with cloud security teams to validate that no other cloud resources are similarly misconfigured. 8) Educate administrators about the risks of hardcoded cloud resource identifiers and enforce best practices for dynamic and secure resource referencing. These steps go beyond generic advice by focusing on the specific misconfiguration vector and the cloud resource ownership validation issue.
Description
A cloud infrastructure misconfiguration in OneLogin AD Connector results in log data being sent to a hardcoded S3 bucket (onelogin-adc-logs-production) without validating bucket ownership. An attacker who registers this unclaimed bucket can begin receiving log files from other OneLogin tenants. These logs may contain sensitive data such as directory tokens, user metadata, and environment configuration. This enables cross-tenant leakage of secrets, potentially allowing JWT signing key recovery and user impersonation.
References
- support.onelogin.com/product-notification/noti-00001768 (opens in a new tab)
- specterops.io/blog/2025/06/10/onelogin-many-issues-how-i-pivoted-from-a-trial-tenant-to-compromising-customer-signing-keys/ (opens in a new tab)
- vulncheck.com/advisories/onelogin-ad-connector-account-compromise (opens in a new tab)