CVE-2004-2761

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory published 2022-04-29. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 9.9%CVSS: 9.8Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed services: Not assessed

A fix is available — apply it.

The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/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
Severity98% × 45%
Exploitation65% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
9.9%
EPSS %ILE
95th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

January 5, 2009

Last Modified

May 28, 2026

Advisory Details (8)

Auto-updated Oct 8, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cert.
cert

VU#836068 - MD5 vulnerable to collision attacks

http://www.kb.cert.org/vuls/id/836068
generic

MD5 Considered Harmful Today: Creating a rogue CA certificate - CXSecurity.com

http://securityreason.com/securityalert/4866
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/42181
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/34281
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/33826
generic🔴 Active Exploitation

MD5 Weaknesses Could Lead to Certificate Forgery - Mozilla Security Blog

http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/
generic
http://securitytracker.com/id?1024697
generic

Home - Par-A-Dox

http://www.doxpara.com/research/md5/md5_someday.pdf

Vendor Advisories for CVE-2004-2761(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibnss3-0d (3.11.5-3ubuntu0.7.10.2) @ gutsy2026-05-30ubuntu
redhatrhpki-util-0:7.3.0-21.el42010-11-08redhat
redhatpki-util-0:8.0.5-1.el5pki2010-11-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× 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.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-24807✓ verified
    First seen Dec 7, 2004

    MD5 - Message Digest Algorithm Hash Collision

    Open source ↗

Related CVEs(same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2010:0837

Frequently asked(5)

What is CVE-2004-2761?
CVE-2004-2761 is a critical vulnerability published on January 5, 2009. The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate.
When was CVE-2004-2761 disclosed?
CVE-2004-2761 was first published on January 5, 2009, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-2761 actively exploited?
CVE-2004-2761 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 9.9% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2004-2761?
CVE-2004-2761 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2004-2761?
A fix for CVE-2004-2761 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2004-2761 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2004-2761

Explore →

Is Your Infrastructure Affected by CVE-2004-2761?

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

Book a Demo →Browse All CVEs