Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

CVE-2020-36465 — generic-array

HIGH

CVE-2020-36465 is a high-severity (CVSS 7.5) vulnerability in generic-array. 1 public exploit reference exists, so weaponization risk is real. A fix is available for generic-array — see the affected versions and patch details below.

Use after free in generic-array

Also known asGHSA-3358-4f7f-p4j4RUSTSEC-2020-0146
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
1 known
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.00%0.58%1.16%1.74%0.3%1.2%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-36465 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

5 pkgs affected
🦀generic-array🦀generic-array🦀generic-array🦀generic-array🦀generic-array

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

Description

An issue was discovered in the generic-array crate before 0.13.3 for Rust. It violates soundness by using the arr! macro to extend lifetimes.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iogeneric-array≥ 0.13.0&&< 0.13.30.13.3cargo update -p generic-array --precise 0.13.3
🦀crates.iogeneric-array≥ 0.12.0&&< 0.12.40.12.4cargo update -p generic-array --precise 0.12.4
🦀crates.iogeneric-array≥ 0.11.0&&< 0.11.20.11.2cargo update -p generic-array --precise 0.11.2
🦀crates.iogeneric-array≥ 0.10.0&&< 0.10.10.10.1cargo update -p generic-array --precise 0.10.1
🦀crates.iogeneric-array≥ 0.8.0&&< 0.9.10.9.1cargo update -p generic-array --precise 0.9.1

Affected Products

1 product · 6 configurations
Application
generic-arraygeneric-array_project
≥ 0.13.0 && < 0.13.3
range
Exploits & PoCs
1

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 generic-array crate before 0.13.3 for Rus…

rustsec.orgNVDAug 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update generic-array to 0.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-36465 is resolved across your whole dependency graph.

  3. Workarounds

    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.

Frequently Asked Questions

An issue was discovered in the generic-array crate before 0.13.3 for Rust. It violates soundness by using the arr! macro to extend lifetimes.
O3 Security · Impact-Aware SCA

Is CVE-2020-36465 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-36465: generic-array — Fixed in 0.13.3