# CVE-2026-77151: lin-snow Ech0 crypto.go MD5Encrypt risky encryption


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-m3r5-hc33-p4wf

## What is CVE-2026-77151?

CVE-2026-77151 is a medium-severity vulnerability in lin-snow Ech0, published on 20 Aug 2026. 

### Official description

A security flaw has been discovered in lin-snow Ech0 up to 5.4.1. Affected by this issue is the function MD5Encrypt of the file internal/util/crypto/crypto.go. Performing a manipulation results in risky cryptographic algorithm. Remote exploitation of the attack is possible. The complexity of an attack is rather high. The exploitation is known to be difficult. Upgrading to version 5.4.2 can resolve this issue. The patch is named 9ce19a3b0d0765086a655f45d3a706ec1810404f. It is recommended to upgrade the affected component.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-310

## Which versions are affected by CVE-2026-77151?


## How do I fix CVE-2026-77151?

No fix has been published for CVE-2026-77151 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77151 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77151 and fix it if it is affected.

What it is: CVE-2026-77151 is a medium-severity vulnerability in lin-snow Ech0, published on 20 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-77151 in the wild and no public exploit code.

Affected product: lin-snow Ech0. 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-2026-77151/ (Markdown: https://insights.sbomify.com/CVE-2026-77151/index.md)
```

## Sources

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

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