CVE-2020-6174Network attack vector

Update trust bypass via duplicate signature key IDs

Published Feb 5, 2020 · Updated Aug 4, 2024

Signature verification bypass in The Update Framework before 0.12.2 allows attackers with one signing key to pass untrusted metadata. The tuf.sig.verify routine counts repeated valid signatures carrying the same authorized key ID as separate approvals instead of enforcing uniqueness. Possession of a single authorized signing key is sufficient to satisfy a higher configured threshold, causing metadata without the required independent signers to be trusted.

CVSS severity9.8
Critical
EPSS probability0.99%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Signature verification bypass in The Update Framework before 0.12.2 allows attackers with one signing key to pass untrusted metadata. The tuf.sig.verify routine counts repeated valid signatures carrying the same authorized key ID as separate approvals instead of enforcing uniqueness. Possession of a single authorized signing key is sufficient to satisfy a higher configured threshold, causing metadata without the required independent signers to be trusted.

The record

CVE
CVE-2020-6174
Published
Feb 5, 2020
Updated
Aug 4, 2024
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-347, T1553.002
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 5, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

9.8GitLab Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1553.002Subvert Trust Controls: Code Signing

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo