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.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.9Exploit: NoneExposed: 0

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

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.9(medium)
EPSS
56.7%
KEV
Not listed

Published

October 14, 2016

Last Modified

May 22, 2026

References (22)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 30× 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.

  1. 2026-07-11 08:22 UTCEPSS rescore
  2. 2026-07-09 19:03 UTCEPSS rescore
  3. 2026-07-08 15:09 UTCEPSS rescore
  4. 2026-07-06 02:19 UTCEPSS rescore
  5. 2026-07-06 02:19 UTCEPSS rescore
  6. 2026-07-04 06:26 UTCEPSS rescore
  7. 2026-07-02 14:00 UTCEPSS rescore
  8. 2026-07-01 15:01 UTCEPSS rescore
  9. 2026-06-29 14:02 UTCEPSS rescore
  10. 2026-06-29 14:02 UTCEPSS rescore
  11. 2026-06-27 03:04 UTCEPSS rescore
  12. 2026-06-25 13:46 UTCEPSS rescore
  13. 2026-06-24 14:01 UTCEPSS rescore
  14. 2026-06-24 14:01 UTCEPSS rescore
  15. 2026-06-23 21:29 UTCEPSS rescore
  16. 2026-06-23 21:29 UTCEPSS rescore
  17. 2026-06-22 14:22 UTCEPSS rescore
  18. 2026-06-21 01:56 UTCEPSS rescore
  19. 2026-06-19 19:22 UTCEPSS rescore
  20. 2026-06-19 19:22 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-16 17:49 UTCEPSS rescore
Show 43 more
  1. 2026-06-16 17:49 UTCEPSS rescore
  2. 2026-06-15 17:44 UTCEPSS rescore
  3. 2026-06-14 23:13 UTCEPSS rescore
  4. 2026-06-13 22:56 UTCEPSS rescore
  5. 2026-06-12 23:08 UTCEPSS rescore
  6. 2026-06-11 13:55 UTCEPSS rescore
  7. 2026-06-10 22:14 UTCEPSS rescore
  8. 2026-06-10 13:17 UTCEPSS rescore
  9. 2026-06-07 15:21 UTCEPSS rescore
  10. 2026-06-06 13:44 UTCEPSS rescore
  11. 2026-06-06 13:44 UTCEPSS rescore
  12. 2026-06-05 22:43 UTCEPSS rescore
  13. 2026-06-05 06:07 UTCEPSS rescore
  14. 2026-06-05 06:07 UTCEPSS rescore
  15. 2026-06-02 20:10 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 00:13 UTCEPSS rescore
  22. 2026-05-31 00:13 UTCEPSS rescore
  23. 2026-05-31 00:13 UTCEPSS rescore
  24. 2026-05-29 13:40 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-27 13:37 UTCEPSS rescore
  28. 2026-05-27 13:37 UTCEPSS rescore
  29. 2026-05-26 13:41 UTCEPSS rescore
  30. 2026-05-26 13:41 UTCEPSS rescore
  31. 2026-05-26 07:16 UTCEPSS rescore
  32. 2026-05-26 07:16 UTCEPSS rescore
  33. 2026-05-24 16:42 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 18:18 UTCEG score recompute
  37. 2026-05-22 18:18 UTCGHSA enrichment
  38. 2026-05-21 22:38 UTCEPSS rescore
  39. 2026-05-20 22:36 UTCEPSS rescore
  40. 2026-05-20 22:36 UTCEPSS rescore
  41. 2026-05-20 11:20 UTCEPSS rescore
  42. 2026-05-20 11:20 UTCEPSS rescore
  43. 2026-05-18 21:29 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 in the National Vulnerability Database on October 14, 2016, with the most recent update on May 22, 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 56.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-4900, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs