# CVE-2026-85750: Piwigo arbitrary file read and remote code execution via insecure image processing

> Attackers can achieve remote code execution and read arbitrary files by uploading malicious images processed by Imagick in Piwigo.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-j9q6-q52g-g8jw

## What is CVE-2026-85750?

CVE-2026-85750 is a high-severity code injection vulnerability in Piwigo, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Piwigo before v16.4.0 is vulnerable to arbitrary file read and remote code execution in image upload handling when using the Imagick library due to insufficient validation and unsafe processing of user-supplied image files. By abusing format confusion (e.g., disguising SVG content as PNG), an attacker can trigger unintended interpretation of embedded SVG elements that reference local files. In more advanced scenarios, the Imagick support for Magick Scripting Language (MSL) may be abused to process attacker-controlled instructions, potentially leading to unauthorized server-side file writes and remote code execution, depending on configuration. This has been patched in 16.4.0.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-85750?


## How do I fix CVE-2026-85750?

No fix has been published for CVE-2026-85750 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85750 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85750 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85750 and fix it if it is affected.

What it is: CVE-2026-85750 is a high-severity code injection vulnerability in Piwigo, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85750 exists.

Affected product: Piwigo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85750/ (Markdown: https://insights.sbomify.com/CVE-2026-85750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85750
- OSV: https://osv.dev/vulnerability/CVE-2026-85750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85750/
Summaries are generated and may contain mistakes; the official description above is the record.