Live › vulnerability › CVE-2026-120204
DeepInfer through 0.1.0 has an unauthenticated /profile endpoint whose output_dir parameter is not restricted, so remote attackers can create directories anywhere the process can write. Attackers can also fill the disk or inodes with trace files and use error messages to map the filesystem.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 18:37 UTC. All times on this page are UTC.
Anyone running DeepInfer (deepseek-ai/DeepInfer) 0.1.0 or earlier with the optional profiling HTTP server turned on (DEEPINFER_PROFILE_HTTP_ENABLE=1), which per the code is off by default. If it is reachable over a network, or from an operator's browser via cross-site GET, someone can make the engine create directories and write trace files wherever the process can write. Setups without the profiling server enabled can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| deepinfer | pip | <= 0.1.0 | – |
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
DeepInfer through 0.1.0 contains a path traversal vulnerability in the unauthenticated /profile endpoint that allows remote attackers to create arbitrary directories via the output_dir parameter. Attackers, including cross-site GET requests from an operator's browser, can write chrome trace files to exhaust disk or inodes and use error messages as a filesystem oracle.
This page as .md · .json · in your agent: get_signal("CVE-2026-120204")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.