high CVSS 7.6 EPSS <0.1%

CVE-2026-32749·Docker vulnerability

SiYuan is a personal knowledge management system. In versions 3.6.0 and below, POST /api/import/importSY and POST /api/import/importZipMd write uploaded archives to a path derived from the multipart filename field without sanitization, allowing an admin to write files to arbitrary locations outside the temp directory - including system paths that enable RCE. This can lead to aata destruction by overwriting workspace or application files, and for Docker containers running as root (common default), this grants full container compromise. This issue has been fixed in version 3.6.1.

Severity
high
Software
Docker
Fixed in
3.6.1
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — higher than 24% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-32749 scores 7.6 on CVSS, so a successful attack would be serious — but at <0.1%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 3.6.1

Fixed in: 3.6.1

How to fix this CVE

Update Docker to version 3.6.1 or later to patch the path traversal vulnerability in the import API endpoints. This vulnerability allows authenticated administrators to write files to arbitrary locations on the host system, potentially leading to remote code execution. Apply the patch immediately, especially for Docker containers running with root privileges, as they face complete system compromise.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /api/import/importSY|POST /api/import/importZipMd.*filename=.*(\.\./|/etc/|/usr/|/var/|/root/|/sys/|/proc/)

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Block POST requests to /api/import/importSY and /api/import/importZipMd that contain multipart form data with filename parameters including path traversal sequences (../, absolute paths starting with /, or known system directories). Implement strict input validation to reject filenames with directory separators and limit file writes to a whitelist of safe locations.

How to check if you are affected

  1. Run `docker --version` to check the installed Docker version and confirm if it is below 3.6.1
  2. Check if the import API endpoints (/api/import/importSY and /api/import/importZipMd) are exposed by examining application logs and firewall rules
  3. Search Docker container logs for POST requests to /api/import/importSY or /api/import/importZipMd with suspicious multipart filenames containing path traversal sequences (../, absolute paths, or system paths)
  4. Verify the patch by running `docker --version` again after update to confirm version is 3.6.1 or higher

FAQ

What is CVE-2026-32749?

CVE-2026-32749 is a path traversal vulnerability in Docker's import API endpoints that allows authenticated administrators to write arbitrary files outside the intended temporary directory, enabling file overwrites and potential remote code execution.

Is CVE-2026-32749 being actively exploited?

No, this vulnerability is not currently listed on the CISA KEV catalog, and no public exploits have been disclosed, though the risk remains high due to the severity of the impact.

What versions of Docker are affected by CVE-2026-32749?

Docker versions 3.6.0 and earlier are vulnerable; version 3.6.1 and later contain the fix.

How do I check if my server is vulnerable to CVE-2026-32749?

Run `docker --version` and verify the version number; if it reports 3.6.0 or lower, your installation is vulnerable and requires immediate patching.

Does Defensia detect CVE-2026-32749?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2026-32749 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.
CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-32749. Free for 1 server.

Get started free