# CVE-2004-2761: Weak cryptography in n/a

> The MD5 algorithm is vulnerable to collision attacks, allowing attackers to spoof X.509 certificates and bypass security checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2009
- **Updated:** 28 May 2026
- **Also known as:** GHSA-2q4p-93p8-q2j6

## What is CVE-2004-2761?

CVE-2004-2761 is a critical vulnerability in n/a, published on 5 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-310, CWE-328 (Use of Weak Hash)

## Which versions are affected by CVE-2004-2761?

It affects 1 product.


Products: Ietf Md5.

## How do I fix CVE-2004-2761?

No fix published yet.

## Is CVE-2004-2761 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2761 exists.

Public exploit code:

- MD5 - Message Digest Algorithm Hash Collision (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2761 and fix it if it is affected.

What it is: CVE-2004-2761 is a critical vulnerability in n/a, published on 5 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2761 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2004-2761/ (Markdown: https://insights.sbomify.com/CVE-2004-2761/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2004-2761
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2004-2761
- OSV: https://osv.dev/vulnerability/CVE-2004-2761

---
From sbomify Insights: https://insights.sbomify.com/CVE-2004-2761/
Summaries are generated and may contain mistakes; the official description above is the record.