How severe is CVE-2020-36213?

CVE-2020-36213 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2020-36213 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-36213?

CVE-2020-36213 affects Abi Stable Project Abi Stable. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-36213?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-36213 published?

CVE-2020-36213 was published on 2021-01-26 and last updated on 2026-06-17.

CVE-2020-36213

CVE-2020-36213 is a high-severity vulnerability in Abi Stable Project Abi Stable with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (68th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Abi Stable Project Abi Stable
Published: 2021-01-26
Last modified: 2026-06-17

Description

An issue was discovered in the abi_stable crate before 0.9.1 for Rust. A retain call can create an invalid UTF-8 string, violating soundness.

Frequently asked questions

What is CVE-2020-36213?: An issue was discovered in the abi_stable crate before 0.9.1 for Rust. A retain call can create an invalid UTF-8 string, violating soundness.
How severe is CVE-2020-36213?: CVE-2020-36213 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2020-36213 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-36213?: CVE-2020-36213 affects Abi Stable Project Abi Stable. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-36213?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-36213 published?: CVE-2020-36213 was published on 2021-01-26 and last updated on 2026-06-17.

References

https://rustsec.org/advisories/RUSTSEC-2020-0105.html

Affected products (1)

cpe:2.3:a:abi_stable_project:abi_stable:*:*:*:*:*:rust:*:*

More vulnerabilities in Abi Stable Project Abi Stable

CVE-2020-36212 — High (CVSS 7.5): An issue was discovered in the abi_stable crate before 0.9.1 for Rust. DrainFilter lacks soundness because of a double…

All CVEs affecting Abi Stable Project Abi Stable →