# CVE-2026-15507: coollabsio Coolify Policy Policies authorization

> Attackers can bypass authorization checks in Coolify's policy handler to perform unauthorized actions, requiring an upgrade to secure the platform.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 12 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-6qvw-24xv-xqw6

## What is CVE-2026-15507?

CVE-2026-15507 is a medium-severity missing authorization vulnerability in coollabsio Coolify, published on 12 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in coollabsio Coolify up to 4.1.1. The impacted element is an unknown function of the file /app/Policies/ of the component Policy Handler. Performing a manipulation results in missing authorization. Remote exploitation of the attack is possible. The exploit is now public and may be used.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-15507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15507 is a medium-severity missing authorization vulnerability in coollabsio Coolify, published on 12 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-15507 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-15507/ (Markdown: https://insights.sbomify.com/CVE-2026-15507/index.md)
```

## Sources

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

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