Quick answers
- Is CVE-2026-86117 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86117 being exploited in the wild.
- How severe is CVE-2026-86117?
- High severity, with a CVSS score of 8.1, published 5 September 2026.
- Which products and versions are affected?
- Coolify Coolify through 4.3.17.
- Is there a fix for CVE-2026-86117?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86117 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86117?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass in the OAuth callback handler (OauthController.php) that fails to verify OAuth provider assertions or bind OAuth identities. The vulnerable code accepts any OAuth response containing an email address and either logs in an existing user with that email or creates a new account, without verifying that the email was actually validated by the OAuth provider or that the user owns it. An attacker can register a victim's email on any enabled OAuth provider and use that to authenticate as the victim. This requires no authentication and only requires network access to the Coolify instance with OAuth login enabled. A patch is available in later versions.
Affected products
- Coolify Coolify through 4.3.17
Timeline
- 2026-09-05: disclosed