Unauthenticated Discord webhook abuse via unvalidated feedback forwarding
Published Jul 6, 2026 · Updated Jul 6, 2026
Unrestricted feedback forwarding in coolLabs Coolify before 4.0.0-beta.474 allows remote attackers to abuse a Discord webhook. The unauthenticated route invokes OtherController::feedback, which forwards the unvalidated content field directly to the configured webhook without throttling. Exploitation requires a reachable instance with the feedback Discord webhook configured; attackers can inject content and exhaust webhook limits.
Summary
What happened
Unrestricted feedback forwarding in coolLabs Coolify before 4.0.0-beta.474 allows remote attackers to abuse a Discord webhook. The unauthenticated route invokes OtherController::feedback, which forwards the unvalidated content field directly to the configured webhook without throttling. Exploitation requires a reachable instance with the feedback Discord webhook configured; attackers can inject content and exhaust webhook limits.
The record
- CVE
- CVE-2026-41899
- Published
- Jul 6, 2026
- Updated
- Jul 6, 2026
- Vendor
- coolLabs
- Product
- Coolify
- Classifications
- CWE-306, CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 6, 2026CVE publishedPublication date reported by the CVE source.
- Jul 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.0.0-beta.474
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Unauthenticated feedback endpoint proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo