Quick answers
- Is CVE-2026-51907 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51907 being exploited in the wild.
- How severe is CVE-2026-51907?
- High severity, with a CVSS score of 8.1, published 2 October 2026.
- Which products and versions are affected?
- TaskingAI v0.3.0.
- Is there a fix for CVE-2026-51907?
- 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-51907 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-51907?
- 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 exists in plugin/app/service/image_storage.py's save_base64_image function, which constructs file paths by directly concatenating a user-controlled project_id parameter without path normalization or validation. An attacker can inject path traversal sequences (e.g., "../../../escape") via the X-Project-Id header in POST requests to /v1/execute to escape the intended storage boundary and write files to arbitrary filesystem locations. No containment checks, path resolution, or rejection of traversal sequences are performed.
Affected products
- TaskingAI TaskingAI v0.3.0
Timeline
- 2026-04-20: disclosed: Vulnerability reported as issue #374 on GitHub
- 2026-10-02: advisory: CVE-2026-51907 published