External risk intelligence

Docat Upload API Arbitrary File Upload Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-61645

Docat is designed specifically as a web application for hosting and serving static documentation. As a web-based documentation server, it is commonly deployed as an internet-facing or externally accessible service to allow public or remote users to access the hosted documentation content via its API.

Unrestricted File Upload

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in Docat, a tool for hosting documentation. This issue could allow an attacker to upload arbitrary files, potentially leading to remote code execution or cross-site scripting attacks that could compromise sensitive data or disrupt services. The main concern is confirming relevance and exposure given the tool's typical deployment context.

  • Upload vulnerability in documentation hosting tool.
  • Could allow code execution and data theft.
  • Confirm if this documentation tool is in use.

Attack Path

How an attacker could exploit the issue

An attacker with low-privileged access to the Docat tool can upload a specially crafted file. This file, by bypassing validation of its path and type, can be used to overwrite critical configuration files or introduce malicious code onto the web server, potentially leading to remote code execution or harmful website redirection.

  • Requires low-privileged authenticated access.
  • Upload API vulnerability to file path/type.
  • Risk of code execution or site compromise.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could upload arbitrary files to the Docat server, potentially overwriting critical configuration files or introducing malicious content. This could lead to unauthorized code execution on the server or enable cross-site scripting attacks targeting users.

  • Sensitive configuration files could be overwritten.
  • Malicious files could be placed on the server.
  • Code execution or cross-site scripting may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Docat tool's arbitrary file upload vulnerability impacts teams responsible for the application's infrastructure and security. Initially, focus on identifying all Docat instances, determining their network exposure, and assessing business criticality. This will help pinpoint the accountable owner and inform a risk-based remediation plan, which may involve coordinating with the vendor or implementing temporary controls if immediate patching is not feasible.

  • Application and infrastructure owners should lead.
  • Verify Docat's reachability and criticality.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Docat?

Docat is a specialized software tool used by developers and technical teams to host and serve versioned static documentation. It provides an API that allows users to upload and organize various versions of project manuals or reference guides, making them easily accessible as a web-based documentation server.

What does CWE-434 mean for CVE-2026-61645?

CWE-434 refers to an Unrestricted Upload of File with Dangerous Type. In the context of this CVE, it means the Docat Upload API fails to properly verify the files users send to the server. Because the system does not check file types or target paths, an attacker can upload files that overwrite server configurations or execute malicious code.

How is this vulnerability triggered?

The vulnerability is triggered when an attacker with low-privileged access interacts with the Docat Upload API to send a malicious file. It is important to note that simply visiting the documentation website does not trigger this flaw; the attacker must have the ability to call the API's upload function to successfully place files on the server.

Is my Docat instance at risk?

Risk depends on your deployment. Halo Surface Signal identifies Docat as a web application typically meant for public or remote access to hosted documentation. If your instance is internet-facing, it is more accessible to external actors; however, all deployments should be checked, as the vulnerability relies on having even low-privileged authenticated access.

How should I respond to this threat?

Start by identifying every Docat instance running in your environment and verifying its network accessibility. Once you have a complete inventory, assess the business criticality of each server. Coordinate with your team to plan a risk-based update, keeping in mind that while version 1.6.0 addresses path traversal, you should evaluate your specific deployment for ongoing risks.

References