How severe is CVE-2020-36466?

CVE-2020-36466 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which products are affected by CVE-2020-36466?

CVE-2020-36466 affects the following products: cgc_project cgc.

How do I patch CVE-2020-36466?

No patch has shipped for CVE-2020-36466 yet — track the cgc_project cgc advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2020-36466 across my infrastructure?

Inventory every cgc_project cgc deployment and check each version against the affected-products list above.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

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

Yes. There are 1 known exploit references for CVE-2020-36466, 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-2020-36466?

CVE-2020-36466 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 61th 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.

Which products and versions are affected by CVE-2020-36466?

CVE-2020-36466 affects cgc_project cgc. Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2020-36466 was published on August 8, 2021 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

MEDIUM severity

CVE-2020-36466 — CGC

MEDIUM

CVE-2020-36466 is a medium-severity (CVSS 5.9) vulnerability in cgc_project cgc. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types.

Published

Aug 8, 2021

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

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

Description

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types.

Affected Products

1 product · 1 configurations

Application

cgccgc_project

≤ 2020-12-10

range

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.

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Pt…

rustsec.orgNVDAug 2021

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every cgc_project cgc deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2020-36466 yet — track the cgc_project cgc advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types.

O3 Security · Runtime Protection

Is CVE-2020-36466 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works

CVE-2020-36466 — CGC

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2020-36466 being exploited in your environment?