# CVE-2026-34171: Coolify: Account takeover via CSRF-able GET endpoint that resets password to attacker-known value

> Attackers can hijack user accounts by tricking victims into visiting a crafted URL that resets their password to a known value.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-389w-cc6x-wr2m

## What is CVE-2026-34171?

CVE-2026-34171 is a high-severity vulnerability in coollabsio coolify, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.471, the GET /invitations/{uuid} endpoint can perform a state-changing password reset using an attacker-known invitation UUID, allowing an attacker who can cause a victim to visit the crafted invitation URL to reset the victim account password to a predictable value. This issue is fixed in version 4.0.0-beta.471.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-34171?


## How do I fix CVE-2026-34171?

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

## Is CVE-2026-34171 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34171 and fix it if it is affected.

What it is: CVE-2026-34171 is a high-severity vulnerability in coollabsio coolify, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-34171 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-2026-34171/ (Markdown: https://insights.sbomify.com/CVE-2026-34171/index.md)
```

## Sources

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

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