CVE-2026-105144 Drogon CVE debrief

Who should care

Defenders and security teams responsible for Drogon deployments on Windows should assess exposure and prioritize remediation. System administrators and developers using Drogon in their applications should verify the presence of the affected function and apply necessary patches or compensating controls.

Why it matters

CVE-2026-105144 is a medium-severity path traversal vulnerability in Drogon on Windows, allowing remote attackers to manipulate the application. Defenders should assess exposure, prioritize remediation, and monitor for potential exploitation.

• Verify exposure of Drogon deployments to path traversal attacks.
• Assess the potential for unauthorized access or data exposure in affected systems.
• Prioritize remediation or compensating controls for systems with internet-exposed Drogon instances.
• Monitor system behavior for anomalies indicating potential exploitation.

Technical summary

The vulnerability is located in the StaticFileRouter::route function of Drogon up to 1.9.13-1/10.0-beta.3 on Windows. A remote attacker can manipulate the application to traverse paths, potentially leading to unauthorized access or data exposure. The CVSS score is 5.5, indicating a medium severity vulnerability. Defenders should assess exposure, prioritize remediation, and monitor for potential exploitation. The exploit has been published, and although the vendor was notified, no response was received. Affected product deployments on Windows should be reviewed for exposure, and compensating controls may be necessary until remediation can be applied.

Defensive priority

Medium priority should be given to assessing exposure and applying remediation, as the vulnerability is publicly exploitable and has a CVSS score of 5.5.

Recommended defensive actions

• Assess exposure by reviewing system inventory and deployment contexts for Drogon up to 1.9.13-1/10.0-beta.3 on Windows.
• Verify the presence of the StaticFileRouter::route function in the affected component.
• Apply remediation or compensating controls as recommended by the vendor or based on industry best practices.
• Monitor for potential exploitation attempts or anomalies in system behavior.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and vector. However, the vendor's response to the disclosure is unknown, and the actual impact of the vulnerability requires further verification.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.