CVE-2025-34063: One Identity OneLogin Active Directory Connector (ADC) · Authentication Bypass by Spoofing
Affects One Identity OneLogin Active Directory Connector (ADC)Source CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| One Identity OneLogin Active Directory Connector (ADC) | Affected
| Fixed in– |
AI-suggested
Immediate mitigation steps include upgrading the OneLogin ADC to version 6.1.5 or later, where the vulnerability is addressed. Until patching is possible, organizations should restrict access to the /api/adc/v4/configuration endpoint by implementing strict network segmentation and access controls, limiting it to trusted administrators only. Monitoring and logging access to this endpoint should be enhanced to detect any anomalous requests that could indicate attempts to retrieve the signing key. Additionally, organizations should rotate all JWT signing keys and invalidate existing tokens to prevent reuse of compromised credentials. Employing multi-factor authentication (MFA) on the OneLogin portal and downstream applications can provide an additional security layer, reducing the risk of unauthorized access even if tokens are forged. Regular security audits and penetration testing focused on identity federation components are recommended to identify and remediate similar weaknesses proactively.
Description
A cryptographic authentication bypass vulnerability exists in OneLogin AD Connector prior to 6.1.5 due to the exposure of a tenant’s SSO JWT signing key via the /api/adc/v4/configuration endpoint. An attacker in possession of the signing key can craft valid JWT tokens impersonating arbitrary users within a OneLogin tenant. The tokens allow authentication to the OneLogin SSO portal and all downstream applications federated via SAML or OIDC. This allows full unauthorized access across the victim’s SaaS environment.
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)