# CVE-2005-4900: SHA-1 is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by atta


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 14 Oct 2016
- **Updated:** 22 May 2026
- **Also known as:** GHSA-xj59-9qjv-fr54, openSUSE-SU-2024:11377-1

## What is CVE-2005-4900?

CVE-2005-4900 is a medium-severity vulnerability in Google Chrome, published on 14 Oct 2016. 

### Official description

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.

Weakness: CWE-326 (Inadequate Encryption Strength), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2005-4900?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sha1collisiondetection` | openSUSE:Tumbleweed | All versions | 1.0.3-4.12 |

Products: Google Chrome.

## How do I fix CVE-2005-4900?

Upgrade to a fixed version.

## Is CVE-2005-4900 being exploited?

There is no known exploitation of CVE-2005-4900 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4900 and fix it if it is affected.

What it is: CVE-2005-4900 is a medium-severity vulnerability in Google Chrome, published on 14 Oct 2016. 
Exploitation: There is no known exploitation of CVE-2005-4900 in the wild and no public exploit code.

Affected product: Google Chrome. 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-2005-4900/ (Markdown: https://insights.sbomify.com/CVE-2005-4900/index.md)
```

## Sources

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

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