External risk intelligence

TaskingAI DALL-E 3 Path Traversal Leads to Arbitrary File Writes.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-51906

TaskingAI is a web-based AI application and development platform. As a server-side tool that processes user inputs for image generation, it is typically deployed as a web service or API endpoint accessible over the network, making the application logic and associated file handling functions commonly reachable in a web-facing deployment context.

Path Traversal

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in a TaskingAI image generation tool could allow unauthorized access to server files if manipulated by attackers. This is a critical issue that requires attention to confirm relevance and potential exposure within your environment.

File writing vulnerability in image tool.
Confirms need to check for relevant use.
Assess exposure to critical server risk.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a specially crafted request to the DALL-E 3 image generation tool. By manipulating the `project_id` parameter, they could trick the `save_url_image` function into writing downloaded images to unintended locations on the server. This could allow the attacker to overwrite sensitive files or place malicious content on the system.

No authentication required to access.
Malicious input in `project_id` parameter.
Arbitrary file write on server filesystem.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to write downloaded images to arbitrary server locations by manipulating a parameter in the image generation tool. This could impact system integrity when the tool is processing image URLs.

Server filesystem data.
Manipulating image URL parameters.
Compromise system files.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership

This vulnerability in TaskingAI's image generation tool requires a coordinated response. Application owners or platform teams responsible for the TaskingAI deployment must first identify all instances of the affected technology. Subsequently, infrastructure and network/security teams should determine the exposure and business criticality of these instances. Finally, the relevant team, potentially including vendor-management if a managed service is involved, must plan and execute remediation based on the assessed risk.

Application or platform teams own the issue.
Verify TaskingAI deployment and network exposure.
Plan remediation based on business criticality.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is TaskingAI?

TaskingAI is a web-based AI platform designed for developing and managing artificial intelligence applications. It provides integrated tools for tasks like image generation, which rely on backend functions to process user requests and handle data storage on the server side.

What does CVE-2026-51906 mean for system security?

This CVE describes a path traversal weakness, categorized as CWE-22. It occurs when the software improperly handles file paths, allowing an attacker to escape intended directories and write files to unauthorized locations on the server's filesystem by manipulating input data.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending a crafted request to the image generation tool where the project_id parameter is specifically modified. Simply accessing the application or navigating its standard interface without this specific parameter manipulation does not trigger the file write issue.

Is my deployment at risk according to Halo Surface Signal?

Halo Surface Signal indicates this is a web-facing issue. Because TaskingAI operates as a network-accessible service that processes external inputs for image generation, any instance exposed to the network is considered reachable and likely to be relevant for review.

What should I do if I use TaskingAI?

Begin by identifying every instance of TaskingAI running in your environment. Once mapped, have your platform or security teams assess the network accessibility of these instances and prioritize them for updates or configuration changes based on their importance to your business operations.

References

github.com/TaskingAI/TaskingAI/issues/375

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.