CVE-2005-4900

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2022-05-01. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 5.9Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 14, 2016

Last Modified

June 16, 2026

Advisory Details (7)

Auto-updated Jul 25, 2026
No fix on record yet.
generic

SHA-1 Broken - Schneier on Security

https://www.schneier.com/blog/archives/2005/02/sha1_broken.html
generic

Google Online Security Blog: Announcing the first SHA1 collision

https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
generic

Google Online Security Blog: An update on SHA-1 certificates in Chrome

https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html
generic

At death’s door for years, widely used SHA1 function is now dead - Ars Technica

https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/
generic
http://www.securityfocus.com/bid/12577
generic

Shattered

http://shattered.io/
generic

Notes on the Wang et al. $2^{63}$ SHA-1 Differential Path

http://ia.cr/2007/474

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 101 total refreshes for this CVE.

  1. 2026-10-09 19:59 UTCEPSS rescore
  2. 2026-10-08 16:32 UTCEPSS rescore
  3. 2026-10-07 23:36 UTCEPSS rescore
  4. 2026-10-06 15:08 UTCEPSS rescore
  5. 2026-10-05 17:37 UTCEPSS rescore
  6. 2026-10-04 23:15 UTCEPSS rescore
  7. 2026-10-03 14:19 UTCEPSS rescore
  8. 2026-09-29 02:52 UTCEG score recompute
  9. 2026-09-18 19:20 UTCEPSS rescore
  10. 2026-09-17 19:20 UTCEPSS rescore
  11. 2026-09-13 16:39 UTCEPSS rescore
  12. 2026-09-12 14:54 UTCEPSS rescore
  13. 2026-09-10 09:23 UTCEPSS rescore
  14. 2026-09-05 15:21 UTCEPSS rescore
  15. 2026-09-04 04:59 UTCEPSS rescore
  16. 2026-08-30 01:14 UTCEPSS rescore
  17. 2026-08-08 16:30 UTCEPSS rescore
  18. 2026-08-05 19:11 UTCEPSS rescore
  19. 2026-08-04 15:03 UTCEPSS rescore
  20. 2026-08-03 10:27 UTCEPSS rescore
  21. 2026-07-24 14:11 UTCEPSS rescore
  22. 2026-07-23 00:49 UTCEG score recompute
  23. 2026-07-23 00:29 UTCEG score recompute
  24. 2026-07-22 23:53 UTCEG score recompute
  25. 2026-07-22 21:33 UTCEG score recompute
Show 75 more
  1. 2026-07-20 17:02 UTCEPSS rescore
  2. 2026-07-18 09:59 UTCEPSS rescore
  3. 2026-07-16 16:58 UTCEPSS rescore
  4. 2026-07-15 16:53 UTCEPSS rescore
  5. 2026-07-15 01:55 UTCEPSS rescore
  6. 2026-07-13 22:25 UTCEPSS rescore
  7. 2026-07-13 06:07 UTCEPSS rescore
  8. 2026-07-13 06:07 UTCEPSS rescore
  9. 2026-07-11 08:22 UTCEPSS rescore
  10. 2026-07-09 19:03 UTCEPSS rescore
  11. 2026-07-08 15:09 UTCEPSS rescore
  12. 2026-07-06 02:19 UTCEPSS rescore
  13. 2026-07-06 02:19 UTCEPSS rescore
  14. 2026-07-04 06:26 UTCEPSS rescore
  15. 2026-07-02 14:00 UTCEPSS rescore
  16. 2026-07-01 15:01 UTCEPSS rescore
  17. 2026-06-29 14:02 UTCEPSS rescore
  18. 2026-06-29 14:02 UTCEPSS rescore
  19. 2026-06-27 03:04 UTCEPSS rescore
  20. 2026-06-25 13:46 UTCEPSS rescore
  21. 2026-06-24 14:01 UTCEPSS rescore
  22. 2026-06-24 14:01 UTCEPSS rescore
  23. 2026-06-23 21:29 UTCEPSS rescore
  24. 2026-06-23 21:29 UTCEPSS rescore
  25. 2026-06-22 14:22 UTCEPSS rescore
  26. 2026-06-21 01:56 UTCEPSS rescore
  27. 2026-06-19 19:22 UTCEPSS rescore
  28. 2026-06-19 19:22 UTCEPSS rescore
  29. 2026-06-18 17:49 UTCEPSS rescore
  30. 2026-06-18 17:49 UTCEPSS rescore
  31. 2026-06-17 17:49 UTCEPSS rescore
  32. 2026-06-17 17:49 UTCEPSS rescore
  33. 2026-06-16 17:49 UTCEPSS rescore
  34. 2026-06-16 17:49 UTCEPSS rescore
  35. 2026-06-15 17:44 UTCEPSS rescore
  36. 2026-06-14 23:13 UTCEPSS rescore
  37. 2026-06-13 22:56 UTCEPSS rescore
  38. 2026-06-12 23:08 UTCEPSS rescore
  39. 2026-06-11 13:55 UTCEPSS rescore
  40. 2026-06-10 22:14 UTCEPSS rescore
  41. 2026-06-10 13:17 UTCEPSS rescore
  42. 2026-06-07 15:21 UTCEPSS rescore
  43. 2026-06-06 13:44 UTCEPSS rescore
  44. 2026-06-06 13:44 UTCEPSS rescore
  45. 2026-06-05 22:43 UTCEPSS rescore
  46. 2026-06-05 06:07 UTCEPSS rescore
  47. 2026-06-05 06:07 UTCEPSS rescore
  48. 2026-06-02 20:10 UTCEPSS rescore
  49. 2026-06-02 20:10 UTCEPSS rescore
  50. 2026-06-01 13:49 UTCEPSS rescore
  51. 2026-06-01 13:49 UTCEPSS rescore
  52. 2026-06-01 13:49 UTCEPSS rescore
  53. 2026-05-31 22:28 UTCEPSS rescore
  54. 2026-05-31 00:13 UTCEPSS rescore
  55. 2026-05-31 00:13 UTCEPSS rescore
  56. 2026-05-31 00:13 UTCEPSS rescore
  57. 2026-05-29 13:40 UTCEPSS rescore
  58. 2026-05-28 13:42 UTCEPSS rescore
  59. 2026-05-28 13:42 UTCEPSS rescore
  60. 2026-05-27 13:37 UTCEPSS rescore
  61. 2026-05-27 13:37 UTCEPSS rescore
  62. 2026-05-26 13:41 UTCEPSS rescore
  63. 2026-05-26 13:41 UTCEPSS rescore
  64. 2026-05-26 07:16 UTCEPSS rescore
  65. 2026-05-26 07:16 UTCEPSS rescore
  66. 2026-05-24 16:42 UTCEPSS rescore
  67. 2026-05-22 21:15 UTCEPSS rescore
  68. 2026-05-22 21:15 UTCEPSS rescore
  69. 2026-05-22 18:18 UTCEG score recompute
  70. 2026-05-22 18:18 UTCGHSA enrichment
  71. 2026-05-21 22:38 UTCEPSS rescore
  72. 2026-05-20 22:36 UTCEPSS rescore
  73. 2026-05-20 22:36 UTCEPSS rescore
  74. 2026-05-20 11:20 UTCEPSS rescore
  75. 2026-05-20 11:20 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2005-4900?
CVE-2005-4900 is a medium vulnerability published on October 14, 2016. 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…
When was CVE-2005-4900 disclosed?
CVE-2005-4900 was first published on October 14, 2016, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-4900 actively exploited?
CVE-2005-4900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2005-4900?
CVE-2005-4900 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2005-4900?
No fix for CVE-2005-4900 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2005-4900

Explore →

Is Your Infrastructure Affected by CVE-2005-4900?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs