# CVE-2025-59363: Information disclosure in OneLogin

> Attackers can retrieve OIDC client secrets via the Apps API, exposing sensitive credentials in OneLogin.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-vm8x-q73p-rmc7

## What is CVE-2025-59363?

CVE-2025-59363 is a high-severity vulnerability in OneLogin, published on 14 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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),

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

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

## Is CVE-2025-59363 being exploited?

There is no known exploitation of CVE-2025-59363 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59363 is a high-severity vulnerability in OneLogin, published on 14 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59363 in the wild and no public exploit code.

Affected product: OneLogin. 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-59363/ (Markdown: https://insights.sbomify.com/CVE-2025-59363/index.md)
```

## Sources

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

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