CVE-2026-86117 json
Coolify through 4.3.17 OAuth Account Takeover via Unverified Email Matching
published 2026-09-05 2 mo ago modified 2026-09-24 46 d ago also EUVD-2026-71949
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
Coolify through 4.3.17 contains an authentication bypass vulnerability in the OAuth callback handler that signs users into existing accounts based solely on email address without verifying provider assertions or binding OAuth identities. Attackers can register a victim's email address on any enabled OAuth provider to obtain authenticated sessions as that user, bypassing password requirements and two-factor authentication.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 1 mo ago
Exploit prediction
0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.2 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 9.2 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- coollabsio coolify
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/geo-chen/oss/blob/main/coolify.md
technical-description
-
github.com
/coollabsio/coolify/blob/v4.3.17/app/Http/Controllers/OauthController.php
technical-description
-
github.com
/coollabsio/coolify/blob/v4.3.17/routes/web.php
technical-description
-
github.com
/coollabsio/coolify
product
-
vulncheck.com
/advisories/coolify-through-4.3.17-oauth-account-takeover-via-unverified-email-matching
third-party-advisory
Sources
- CVE List CVE-2026-86117
- NVD CVE-2026-86117
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.