No exploitation reportedFix available

CVE-2020-15093

Q: Is CVE-2020-15093 actively exploited?

Active exploitation of CVE-2020-15093 has not been confirmed. Its EPSS score was 1.4% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2020-15093?

CVE-2020-15093 has a CVSS v3 base score of 8.6 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N.

No exploitation reported by the sources we read.

Published2020-07-09
Fixed in0.7.1
WeaknessCWE-347

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The tough library (Rust/crates.io) prior to version 0.7.1 does not properly verify the threshold of cryptographic signatures. It allows an attacker to duplicate a valid signature in order to circumvent TUF requiring a minimum threshold of unique signatures before the metadata is considered valid. A fix is available in version 0.7.1. CVE-2020-6174 is assigned to the same vulnerability in the TUF reference implementation.

Timeline

dates in UTC

2020-07-0919:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-15093?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-15093?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV

Amazon tough

Branch	Affected	Fixed in	Source
0.7	< 0.7.1	0.7.1	NVD · OSV
0.x	≥ 0.0.0-0, < 0.7.1	0.7.1	OSV

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Update Amazon tough to 0.7.1

Advisories and patches

github.comPatch
github.comPatch

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

CNACVSS 3.18.6read 2026-10-23
NVDCVSS 3.18.6read 2026-10-23
NVDCVSS 2.05read 2026-10-23
CNAweakness (CWE)CWE-347read 2026-10-23
NVDweakness (CWE)CWE-347read 2026-10-23
FIRST EPSSEPSS score1.4 %2026-10-23
OSVaffected packages—

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Published: 2020-07-09
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2020-15093?

Is CVE-2020-15093 actively exploited?

Active exploitation of CVE-2020-15093 has not been confirmed. Its EPSS score was 1.4% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-15093?

CVE-2020-15093 has a CVSS v3 base score of 8.6 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N.

Running tough? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database