# CVE-2025-34063: OneLogin AD Connector JWT Authentication Bypass via Exposed Signing Key

> Attackers can bypass authentication and impersonate users by exploiting an exposed JWT signing key, gaining unauthorized access to SSO portals and federated applications.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2025
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-g2mv-fq56-3w42

## What is CVE-2025-34063?

CVE-2025-34063 is a critical authentication bypass vulnerability in OneLogin Active Directory Connector (ADC), published on 1 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2025-34063?


## How do I fix CVE-2025-34063?

No fix has been published for CVE-2025-34063 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34063 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34063 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34063 and fix it if it is affected.

What it is: CVE-2025-34063 is a critical authentication bypass vulnerability in OneLogin Active Directory Connector (ADC), published on 1 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34063 exists.

Affected product: OneLogin Active Directory Connector (ADC). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34063/ (Markdown: https://insights.sbomify.com/CVE-2025-34063/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34063
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34063
- OSV: https://osv.dev/vulnerability/CVE-2025-34063

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34063/
Summaries are generated and may contain mistakes; the official description above is the record.