DeepInfer through 0.1.0 Path Traversal via /profile output_dir Parameter
Only affects DeepInfer through 0.1.0 when DEEPINFER_PROFILE_HTTP_ENABLE=1 is set and the profiling endpoint is reachable from other hosts. CVSS rates it 6.3 (medium); no vendor rating or fix is listed.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
DeepInfer, an inference tool, is affected through its unauthenticated /profile endpoint, which lets remote attackers, including through cross-site requests from an operator's browser, create arbitrary directories and write trace files. This can exhaust disk space or inodes and expose information about the server's filesystem through error messages.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- deepseek-ai DeepInfer
through 0.1.0
References 4
GitHub · deepseek-ai/DeepInfer
Questions about CVE-2026-120204
What does this mean?
The output_dir parameter on the /profile endpoint is not restricted, so a request can make DeepInfer create arbitrary directories and write large chrome trace files. This can fill the disk, and error messages can reveal information about the filesystem.Source: github.com
Am I affected, and how do I check?
DeepInfer versions through 0.1.0 are in the listed range. The exposure requires DEEPINFER_PROFILE_HTTP_ENABLE=1 to be set, which enables the profiling HTTP endpoint, and that endpoint must be reachable from other hosts on the network. Check the environment of the running service for that variable and whether the endpoint can be reached from other hosts.Source: github.com
What should I do about it?
The facts do not list a fixed version, so no upgrade target is given. Check the vendor's release notes or advisory for a version later than 0.1.0 that contains a fix before relying on one.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data