CVE-2005-4900

5.9 MEDIUM 0.9% exploit odds No fix listed

What it is

SHA-1 is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of SHA-1 in TLS 1.2. NOTE: this CVE exists to provide a common identifier for referencing this SHA-1 issue; the existence of an identifier is not, by itself, a technology recommendation.

At a glance

Exploitability: Can be exploited over the network without logging in. High risk of data exposure.
Exploit odds: 0.9% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2016-10-14 16:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-16 22:19 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.9% in the next 30 days (EPSS).
Severity: 5.9 MEDIUM (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2016-10-14 16:59 UTC
Last modified: 2026-06-16 22:19 UTC
Exploit probability: 0.9% · EPSS, next 30 days
Weakness: CWE-326 · Inadequate encryption strength
Record status: Modified

Affected

Google Chrome ≤ 47.0.2526.111

Attack profile CVSS 3.1 · 5.9

Attack vector: Network
Complexity: High
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2005-4900.md and follow it. Check whether this project is affected by CVE-2005-4900. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record