# CVE-2026-42147: Coolify: SSRF via S3 Storage Endpoint in testConnection()

> Authenticated users can exploit S3 endpoint validation to force Coolify to make requests to internal or metadata services.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-pwm4-w33c-wjf3

## What is CVE-2026-42147?

CVE-2026-42147 is a medium-severity server-side request forgery vulnerability in coollabsio coolify, published on 7 Jul 2026. An attacker needs administrator access to exploit it, 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.474, S3 storage endpoint validation only checks URL format and testConnection() sends a server-side request to the configured endpoint, allowing an authenticated user with storage management permissions to make Coolify request internal or metadata-service URLs. This issue is fixed in version 4.0.0-beta.474.

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

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


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

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

## Is CVE-2026-42147 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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