Skip to main content
Vulnerability Database/CVE-2026-105144

CVE-2026-105144: Drogon Static File Router Path Traversal

CVE-2026-105144 is a path traversal vulnerability in Drogon framework affecting versions up to 1.9.13-1 and 10.0-beta.3 on Windows. Attackers can exploit the Static File Router to access unauthorized files. This article covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-105144 Overview

CVE-2026-105144 is a path traversal vulnerability [CWE-22] in the Drogon C++ web application framework on Windows. The flaw resides in the StaticFileRouter::route function within lib/src/StaticFileRouter.cc, part of the Static File Router component. An unauthenticated remote attacker can craft requests that escape the intended static file directory and access files outside the web root. The issue affects Drogon versions up to 1.9.13-1/10.0-beta.3. According to the public disclosure, the exploit has been published and the vendor did not respond to pre-disclosure contact.

Critical Impact

Remote attackers can read arbitrary files accessible to the Drogon process on Windows hosts by manipulating static file paths.

Affected Products

  • Drogon framework up to version 1.9.13-1
  • Drogon framework 10.0-beta.3
  • Windows deployments using the StaticFileRouter component

Discovery Timeline

  • 2026-10-04 - CVE-2026-105144 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-105144

Vulnerability Analysis

Drogon is a C++17/20 HTTP application framework that serves static assets through its StaticFileRouter component. The router maps incoming request paths to files on disk under a configured document root. CVE-2026-105144 arises because the StaticFileRouter::route function in lib/src/StaticFileRouter.cc fails to normalize or sufficiently validate request paths on Windows before resolving them against the filesystem. Attackers can submit traversal sequences in the URL path to reach files outside the intended static directory.

The impact is limited to confidentiality on the local host based on the published CVSS metrics, which indicate low confidentiality impact without integrity or availability consequences. Reachable targets depend on the privileges of the Drogon process and the layout of the filesystem, but typically include application source files, configuration files, and credentials stored on the same volume.

Root Cause

The root cause is improper limitation of a pathname to a restricted directory [CWE-22]. On Windows, path handling must account for backslash separators, alternate data streams, drive-relative paths, and 8.3 short names in addition to the standard ../ sequences handled on POSIX. The StaticFileRouter::route implementation does not canonicalize the resolved path and verify it remains within the configured static directory before serving file content.

Attack Vector

Exploitation requires only network access to a vulnerable Drogon server configured to serve static files on Windows. No authentication or user interaction is required. An attacker issues an HTTP GET request against the static route with encoded traversal sequences in the URL path. When the router resolves the request, it reads a file outside the document root and returns the contents in the HTTP response. Public exploit code is referenced in the VulDB entry for this CVE.

See the VulDB entry for CVE-2026-105144 and the VulDB vulnerability record #413369 for additional technical context.

Detection Methods for CVE-2026-105144

Indicators of Compromise

  • HTTP request logs containing ..\, ../, URL-encoded %2e%2e%2f, or double-encoded traversal sequences against static file routes
  • Successful 200 OK responses to static requests whose paths reference files outside the configured document root
  • Access log entries requesting Windows-specific paths such as C:\Windows\win.ini or application configuration files via the static handler

Detection Strategies

  • Inspect Drogon access logs for anomalous static-file requests containing traversal patterns and alert on high response sizes paired with suspicious paths
  • Deploy a web application firewall rule set that blocks encoded and raw path traversal sequences on routes handled by StaticFileRouter
  • Baseline the set of files normally served from the static directory and alert when the server returns content outside that set

Monitoring Recommendations

  • Forward Drogon HTTP logs to a centralized analytics platform and correlate traversal attempts against source IP reputation
  • Monitor file access telemetry on the Windows host for the Drogon process reading files outside its configured static root
  • Track outbound response sizes on static endpoints to identify exfiltration of large configuration or credential files

How to Mitigate CVE-2026-105144

Immediate Actions Required

  • Identify Windows hosts running Drogon with StaticFileRouter enabled and inventory the configured static directories
  • Place a reverse proxy or WAF in front of affected services to reject requests containing path traversal sequences
  • Disable the Drogon static file handler and serve assets from a hardened upstream web server where feasible

Patch Information

No vendor patch is referenced in the published advisory. VulDB reports the vendor was contacted early about this disclosure but did not respond. Monitor the Drogon project for updates addressing StaticFileRouter::route path handling on Windows and apply fixes once released.

Workarounds

  • Remove or restrict registration of static file routes in Drogon configuration until a fix is available
  • Enforce an allowlist of permitted static file extensions and filenames at the reverse proxy layer
  • Run the Drogon process under a low-privilege Windows account with filesystem ACLs that deny read access to sensitive directories
  • Normalize and reject request paths containing .., backslashes, or encoded traversal sequences before they reach Drogon
bash
# Example NGINX reverse proxy rule to block traversal before Drogon
location /static/ {
    if ($request_uri ~* "(\.\.|%2e%2e|\\)") {
        return 400;
    }
    proxy_pass http://drogon_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.