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

Back
New CVE Detected

CVE-2026-72871 – Authentication Bypass (GitHub App Provider Injection) – Dokploy before 0.29.13

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-72871 is a Missing Authentication for Critical Function (CWE-306) vulnerability in Dokploy, a self-hostable Platform-as-a-Service. An unauthenticated GitHub App setup callback endpoint trusts organization and user identifiers supplied in the request, letting a remote attacker inject a malicious GitHub App provider into another organization. It affects Dokploy versions prior to 0.29.13 and is rated High severity (CVSS 7.5).

Technical details

  • Root cause: The /api/providers/github/setup route operates outside the application’s authentication layer, performing no session validation, no CSRF check, and no verification that the organizationId and userId values (taken from the request/state parameter) belong to the caller.
  • Trigger conditions: An attacker sends a crafted request to the GitHub App setup callback endpoint with attacker-chosen organizationId and userId values; no authentication or user interaction is required.
  • Attack vector: Network — the endpoint is remotely reachable without credentials.
  • Impact: An attacker can insert a GitHub App provider containing client_secret, webhook_secret, and PEM private key material into another organization. This can enable deployment from attacker-controlled repositories and triggering of deployments via webhook secrets, with cross-tenant risk in multi-tenant deployments. Impact is to integrity (CVSS C:N/I:H/A:N).

Affected software

  • Dokploy versions prior to 0.29.13

Severity

  • CVSS v3.1 base score: 7.5 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Dokploy 0.29.13 or later, which fixes the issue.
  • If no patch: Restrict network access to the Dokploy instance and its provider setup endpoints (e.g., place the management interface behind a VPN or IP allowlist), and review configured GitHub App providers for unexpected or unauthorized entries.

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: Dokploy
  • Raw response body: id="login-form", Enter your email and password to sign in, Sign in with Passkey
  • JavaScript objects present once the page runs: /docker-container-terminal, /docker-container-logs

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