# CVE-2016-3718: ImageMagick Server-Side Request Forgery (SSRF)

> Remote attackers can perform server-side request forgery attacks via crafted images in ImageMagick's HTTP and FTP coders.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 May 2016
- **Updated:** 21 Oct 2025
- **Also known as:** DEBIAN-CVE-2016-3718, GHSA-q994-gg9f-3g56, UBUNTU-CVE-2016-3718

## What is CVE-2016-3718?

CVE-2016-3718 is a medium-severity server-side request forgery vulnerability in Canonical Ubuntu Linux, published on 5 May 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The (1) HTTP and (2) FTP coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to conduct server-side request forgery (SSRF) attacks via a crafted image.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2016-3718?

It affects 30 products.


Products: Canonical Ubuntu Linux, Imagemagick Imagemagick, Opensuse Leap, Opensuse Opensuse, Oracle Linux, Oracle Solaris, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Big Endian, Redhat Enterprise Linux for Power Big Endian Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux Hpc Node, Redhat Enterprise Linux Hpc Node Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server From Rhui, Redhat Enterprise Linux Server Supplementary Eus and 10 more.

## How do I fix CVE-2016-3718?

Upgrade to a fixed version. US federal agencies must fix it by 3 May 2022.

## Is CVE-2016-3718 being exploited?

Yes. Attackers have exploited CVE-2016-3718 in the wild since at least 3 Nov 2021.

Public exploit code:

- ImageMagick 7.0.1-0 / 6.9.3-9 - 'ImageTragick ' Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3718 and fix it if it is affected.

What it is: CVE-2016-3718 is a medium-severity server-side request forgery vulnerability in Canonical Ubuntu Linux, published on 5 May 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2016-3718 in the wild since at least 3 Nov 2021.

Affected product: Canonical Ubuntu Linux. 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-2016-3718/ (Markdown: https://insights.sbomify.com/CVE-2016-3718/index.md)
```

## Sources

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

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