How severe is CVE-2016-3714?

CVE-2016-3714 has a CVSS score of 8.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-3714?

Affected package information for CVE-2016-3714 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2016-3714?

No fixed version has been published for CVE-2016-3714 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2016-3714 actively exploited in the wild?

Yes. There are 10 known exploit references for CVE-2016-3714, including 2 documented proof-of-concept exploits on Exploit-DB and 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-3714?

CVE-2016-3714 has an EPSS (Exploit Prediction Scoring System) score of 93.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2016-3714 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2016-3714 (ImageMagick Improper Input Validation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-09-09. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-09-30. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2016-3714?

CVE-2016-3714 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-3714 published, and has it been updated?

CVE-2016-3714 was published on May 5, 2016 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2024-09-09 — agencies required to remediate by 2024-09-30

CVE-2016-3714

HIGH

Published

May 5, 2016

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

10 known

EPSS Exploitation Probability

via FIRST.org ↗

93.6%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

The (1) EPHEMERAL, (2) HTTPS, (3) MVG, (4) MSL, (5) TEXT, (6) SHOW, (7) WIN, and (8) PLT coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to execute arbitrary code via shell metacharacters in a crafted image, aka "ImageTragick."

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-39767dosmultiple

ImageMagick 7.0.1-0 / 6.9.3-9 - 'ImageTragick ' Multiple Vulnerabilities

by Nikolay Ermishkin · May 4, 2016

Exploit-DB Source

EDB-39791localmultiple✓ Verified

ImageMagick 6.9.3-9 / 7.0.1-0 - 'ImageTragick' Delegate Arbitrary Command Execution (Metasploit)

by Metasploit · May 9, 2016

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-3714 in your stack?

O3 detects CVE-2016-3714 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works