# CVE-2025-64421: Coolify has a privilege escalation - low privileged user can invite themselves as an admin user

> A low-privileged user can escalate to administrator by exploiting a race condition in the invitation process, allowing full system takeover.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 5 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-4p6r-m39m-9cm9

## What is CVE-2025-64421?

CVE-2025-64421 is a high-severity vulnerability in coollabsio coolify, published on 5 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. In Coolify versions up to and including v4.0.0-beta.434, a low privileged user (member) can invite a high privileged user. At first, the application will throw an error, but if the attacker clicks the invite button a second time, it actually works. This way, a low privileged user can invite themselves as an administrator to the Coolify instance. After the high privileged user is invited, the attacker can initiate a password reset and log in with the new admin. As of time of publication, it is unclear if a patch is available.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Coollabs Coolify.

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

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

## Is CVE-2025-64421 being exploited?

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

## 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-64421 and fix it if it is affected.

What it is: CVE-2025-64421 is a high-severity vulnerability in coollabsio coolify, published on 5 Jan 2026. 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-64421 in the wild and no public exploit code.

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

## Sources

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

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