Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-86117 – OAuth Authentication Bypass / Account Takeover – Coolify through 4.3.17

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86117 is an improper authentication (CWE-287) vulnerability in Coolify, a self-hosted deployment platform, affecting all versions through 4.3.17. The flaw resides in the OAuth callback handler, which authenticates users based solely on email address matching without verifying the identity provider’s email-verification status or binding OAuth identities to accounts. This allows an attacker to take over a victim’s account, bypassing password and two-factor authentication requirements.

Technical details

  • Root cause: OauthController@callback resolves the local account via User::whereEmail(...) on the email returned by the OAuth provider and calls Auth::login($user) directly, without confirming the provider verified that email or linking the OAuth identity to a specific account.
  • The login also bypasses the application’s normal two-factor authentication (Fortify) pipeline.
  • Trigger conditions: the target Coolify instance must have at least one OAuth provider enabled (e.g., GitLab); the attacker must be able to register or control an account on that provider using the victim’s email address.
  • Attack vector: network, unauthenticated — the attacker initiates OAuth login (/auth/{provider}/redirect) and completes the callback (/auth/{provider}/callback) using an OAuth identity set to the victim’s email, receiving an authenticated session as that victim.
  • Impact: full account takeover, including potentially administrative accounts, without needing the victim’s password or 2FA code.

Affected software

  • Coolify (coollabsio/coolify): all versions from the initial release through 4.3.17, when OAuth login is enabled.

Severity

  • CVSS v3.1: 8.1 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0: 9.2 (Critical) — 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

Mitigation and recommended actions

  • Immediate: upgrade to a Coolify release beyond 4.3.17 once a vendor fix confirming provider email verification and OAuth-identity binding is available; monitor the coollabsio/coolify GitHub advisories and release notes for the specific patched version.
  • If no patch is yet applied: disable OAuth login providers on internet-exposed Coolify instances until patched, enforce strict email domain allow-lists on any configured OAuth provider, and audit existing accounts/sessions for unexpected logins.
  • Additional hardening: restrict network access to the Coolify management interface to trusted IPs/VPN, and review audit logs for OAuth callback activity from unfamiliar sources.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Coolify
  • Raw response body: Coolify appearing near self-hosted, deployment, deployments, servers, or projects

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge