How severe is CVE-2020-3716?

CVE-2020-3716 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-3716?

CVE-2020-3716 affects the following packages: magento/community-edition (Packagist), magento/community-edition (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-3716?

Update magento/community-edition to 2.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-3716 is resolved across your whole dependency graph.

How do I detect CVE-2020-3716 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-3716 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2020-3716 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-3716 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-3716?

CVE-2020-3716 has an EPSS (Exploit Prediction Scoring System) score of 14.0%, placing it in the 97th 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. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2020-3716?

CVE-2020-3716 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2020-3716 published, and has it been updated?

CVE-2020-3716 was published on January 29, 2020 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2020-3716 — community-edition

CRITICAL

CVE-2020-3716 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in magento/community-edition. EPSS puts its 30-day exploitation probability at 14.0% (97th percentile). A fix is available for magento/community-edition — see the affected versions and patch details below.

Magento deserialization vulnerability

Also known asBIT-magento-2020-3716GHSA-9wc9-498w-h8xv

Published

Jan 29, 2020

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

14.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘magento/community-edition🐘magento/community-edition

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Magento versions 2.3.3 and earlier, 2.2.10 and earlier, 1.14.4.3 and earlier, and 1.9.4.3 and earlier have a deserialization of untrusted data vulnerability. Successful exploitation could lead to arbitrary code execution.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 2.2.0&&< 2.2.11	2.2.11`composer require magento/community-edition:^2.2.11`
🐘Packagist	`magento/community-edition`	≥ 2.3.0&&< 2.3.4	2.3.4`composer require magento/community-edition:^2.3.4`

Affected Products

1 product · 6 configurations

Application

magentomagento

≥ 2.3.0 && ≤ 2.3.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update magento/community-edition to 2.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-3716 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-3716 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-502Deserialization of Untrusted Data

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

magento2

6.2/10

Maintained10/10

Code-Review1/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Jan 29, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-3716

GHSA-9wc9-498w-h8xv

BIT-magento-2020-3716

References

Advisorynvd.nist.gov · CVE 2020 3716 Fixhelpx.adobe.com · apsb20 02 Packagegithub.com · magento2

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs affecting magento/community-edition is rated as high or higher (top: critical).

CVE-2025-54264CVE-2025-54263CVE-2025-54266CVE-2025-54267CVE-2025-54265CVE-2025-54236CVE-2025-49555CVE-2025-49556

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-3716 — community-edition

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2020-3716 in your dependencies?