Account takeover via unverified OAuth email matching
Published Sep 5, 2026 · Updated Sep 10, 2026
Authentication bypass in coolLabs Coolify 4.3.17 and earlier allows remote attackers to take over accounts through an enabled OAuth provider. OauthController::callback lowercases the provider-supplied email, selects the first local user with that address, and calls Auth::login without verifying or binding the provider identity. An attacker must control the victim's email address at an enabled provider; a successful flow bypasses the password and two-factor authentication.
Summary
What happened
Authentication bypass in coolLabs Coolify 4.3.17 and earlier allows remote attackers to take over accounts through an enabled OAuth provider. OauthController::callback lowercases the provider-supplied email, selects the first local user with that address, and calls Auth::login without verifying or binding the provider identity. An attacker must control the victim's email address at an enabled provider; a successful flow bypasses the password and two-factor authentication.
The record
- CVE
- CVE-2026-86117
- Published
- Sep 5, 2026
- Updated
- Sep 10, 2026
- Vendor
- coolLabs
- Product
- Coolify
- Classifications
- CWE-287, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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=0 <=4.3.17
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- OAuth email-matching feature-test 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