# CVE-2026-41899: Coolify unauthenticated feedback endpoint allows Discord webhook abuse

> Unauthenticated feedback endpoint allows attackers to spam Discord webhooks and inject content, requiring an upgrade to Coolify.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-v64c-v633-58xp

## What is CVE-2026-41899?

CVE-2026-41899 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, 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, POST /api/feedback has no authentication, no rate limiting, and no input validation, allowing arbitrary content to be forwarded directly to a Discord webhook and enabling spam, content injection, and webhook abuse. This issue is fixed in version 4.0.0-beta.474.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-41899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41899 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41899 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-41899/ (Markdown: https://insights.sbomify.com/CVE-2026-41899/index.md)
```

## Sources

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

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