# CVE-2026-51906: TaskingAI DALL-E 3 path traversal in save_url_image

Source: https://junglewise.ai/threats/cve-2026-51906-in-taskingai-v0-3-0-in-the-dall-e-3-image-generation-tool-save  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-02. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-51906 · Severity: info · Published 2026-10-02

TaskingAI's DALL-E 3 image generation tool contains a path traversal flaw in the save_url_image function that allows attackers to write downloaded images to arbitrary locations on the server by manipulating the project_id parameter. This could enable attackers to overwrite critical system files, inject malicious content, or access restricted directories on the server filesystem.

Technologies: [TaskingAI](https://junglewise.ai/threats/technologies/taskingai). Vendors: [TaskingAI](https://junglewise.ai/threats/vendors/taskingai).

## Quick answers

**Is CVE-2026-51906 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-51906 being exploited in the wild.

**How severe is CVE-2026-51906?** Informational severity, published 2 October 2026.

**Which products and versions are affected?** TaskingAI v0.3.0.

**Is there a fix for CVE-2026-51906?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-51906 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-51906?** Check whether you run TaskingAI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a CWE-22 path traversal in the save_url_image function (plugin/app/service/image_storage.py:64) where user-controlled project_id parameter is concatenated directly into file paths without validation or normalization. An unauthenticated attacker can inject sequences like "../../../" via the X-Project-Id header in POST requests to /v1/execute to write files outside the intended storage directory. A fix exists in the repository (Issue #375 indicates this is being addressed).

## Affected products

- TaskingAI TaskingAI v0.3.0

## Timeline

- 2026-04-20: disclosed
- 2026-10-02: advisory

## References

- [https://gist.github.com/Ro1ME/3430171ed3a7e6c42864f45b59c203cf](https://gist.github.com/Ro1ME/3430171ed3a7e6c42864f45b59c203cf)
- [https://github.com/TaskingAI/TaskingAI/issues/375](https://github.com/TaskingAI/TaskingAI/issues/375)

## Related threats

- [TaskingAI server-side request forgery in OpenAPI action handling](https://junglewise.ai/threats/cve-2026-111321-taskingai-through-0-3-0-contains-a-server-side-request-forgery)
- [TaskingAI QR Code Generator path traversal in image storage](https://junglewise.ai/threats/cve-2026-51907-in-taskingai-v0-3-0-in-the-qr-code-generator-plugin-save-base64)