How severe is CVE-2021-36564?

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

Which packages are affected by CVE-2021-36564?

CVE-2021-36564 affects the following packages: topthink/framework (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-36564?

Update topthink/framework to 6.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-36564 is resolved across your whole dependency graph.

How do I detect CVE-2021-36564 in my Packagist dependencies?

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

How do I mitigate CVE-2021-36564 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-2021-36564 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2021-36564, including 1 in-the-wild exploitation 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-2021-36564?

CVE-2021-36564 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 79th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-36564?

CVE-2021-36564 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-2021-36564 published, and has it been updated?

CVE-2021-36564 was published on December 6, 2021 and was last updated on July 8, 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-2021-36564 — framework

CRITICAL

CVE-2021-36564 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in topthink/framework. 1 public exploit reference exists, so weaponization risk is real. A fix is available for topthink/framework — see the affected versions and patch details below.

Deserialization of Untrusted Data in topthink/framework

Also known asGHSA-33gc-6cw9-w3g4

Published

Dec 6, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2021-36564 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘topthink/framework

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

ThinkPHP v6.0.8 was discovered to contain a deserialization vulnerability via the component vendor\league\flysystem-cached-adapter\src\Storage\Adapter.php.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`topthink/framework`	all versions	6.0.9`composer require topthink/framework:^6.0.9`

Affected Products

1 product · 1 configurations

Application

thinkphpthinkphp

1 version

6.0.8

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.

ThinkPHP v6.0.8 was discovered to contain a deserialization vulnerabilit…

github.comNVDDec 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for topthink/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update topthink/framework to 6.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-36564 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

ThinkPHP v6.0.8 was discovered to contain a deserialization vulnerability via the component vendor\league\flysystem-cached-adapter\src\Storage\Adapter.php.

O3 Security · Impact-Aware SCA

Is CVE-2021-36564 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 known public exploit tooling found.

OpenSSF Scorecard

Package health score

framework

2.9/10

Code-Review0/10

Maintained0/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Dec 6, 2021

First exploit

Dec 7, 2021

1 day after disclosure — rapid exploitation

Last updated

Jul 8, 2026

Identifiers

CVE-2021-36564

GHSA-33gc-6cw9-w3g4

References

Advisorynvd.nist.gov Evidencegithub.com

Related vulnerabilities

This CVE is critical severity; 6 of 8 other CVEs affecting topthink/framework are rated as high or higher (top: critical).

CVE-2025-50706CVE-2024-44902CVE-2024-34467CVE-2022-47945CVE-2022-44289CVE-2022-38352CVE-2022-33107CVE-2018-17566

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2021-36564 — framework

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-2021-36564 in your dependencies?