# CVE-2026-34170: Coolify: Server-Side Request Forgery via attacker-controlled GitHub App API URL

> An authenticated user can exploit a Server-Side Request Forgery vulnerability in Coolify to access internal services or cloud metadata endpoints.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-3g6r-cxv5-3c7h

## What is CVE-2026-34170?

CVE-2026-34170 is a medium-severity server-side request forgery vulnerability in coollabsio coolify, published on 7 Jul 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. Prior to 4.0.0-beta.471, the GithubApp api_url field is used as the base URL for server-side HTTP requests without allowlisting or private IP blocking, allowing an authenticated user to configure a GitHub App source that causes Coolify to request internal services or cloud metadata endpoints. This issue is reported as fixed in version 4.0.0-beta.471.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-34170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34170 is a medium-severity server-side request forgery vulnerability in coollabsio coolify, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34170 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-2026-34170/ (Markdown: https://insights.sbomify.com/CVE-2026-34170/index.md)
```

## Sources

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

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