# CVE-2025-22607: Coolify Vulnerable to GitHub / GitLab OAuth Secrets Leak

> Authenticated users can access sensitive OAuth secrets for any GitHub or GitLab configuration by guessing UUIDs, requiring an upgrade to Coolify.

- **Severity:** Medium 4.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2025
- **Updated:** 24 Jan 2025
- **Also known as:** GHSA-8w24-gfgq-jg72

## What is CVE-2025-22607?

CVE-2025-22607 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.361, the missing authorization allows any authenticated user to fetch the details page for any GitHub / GitLab configuration on a Coolify instance by only knowing the UUID of the model. This exposes the "client id", "client secret" and "webhook secret." Version 4.0.0-beta.361 fixes this issue.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Coollabs Coolify.

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

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

## Is CVE-2025-22607 being exploited?

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

## Other vulnerabilities in coollabsio coolify

- [CVE-2025-59157](https://insights.sbomify.com/CVE-2025-59157/): Coolify has Git Repository RCE (critical 10.0)
- [CVE-2025-64420](https://insights.sbomify.com/CVE-2025-64420/): Coolify members can see private key of root user (critical 10.0)
- [CVE-2025-66209](https://insights.sbomify.com/CVE-2025-66209/): Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup (critical 10.0)
- [CVE-2025-22609](https://insights.sbomify.com/CVE-2025-22609/): Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE) (critical 10.0)
- [CVE-2025-22611](https://insights.sbomify.com/CVE-2025-22611/): Coolify vulnerable to Privilege Escalation resulting in Remote Command Execution (RCE) (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22607 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22607 exists.

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

## Sources

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

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