Cross-Site Request Forgery (CSRF) in Coolify (CVE-2026-34171)
Summary
Vulnerability in Coolify (CVE-2026-34171). Confidential information can be exposed externally. Exploitable via GET /invitations/{uuid}.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-34171 has been found in Coolify.
Attackers can target a specific entry point like GET /invitations/{uuid} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Coolify CVE-2026-34171" on the vendor's site.
CVE-2026-34171 (Coolify) — CWE-352 / CVSS v3 8.0
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /invitations/{uuid}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in Coolify. Attackers reach the vulnerable code path via GET /invitations/{uuid} without authentication.
Check the vendor advisory for the affected versions of Coolify. Attack surface: GET /invitations/{uuid}.
Severity: High (CVSS 8.0/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /invitations/{uuid} requests with malformed payloads or SQL meta-characters. Run grep -r 'Coolify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Coolify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Coolifyを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /invitations/{uuid}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /invitations/{uuid}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /invitations/{uuid} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com