# CVE-2025-66692: Memory corruption in n/a

> Attackers can cause a Denial of Service in Trust Wallet Core via a buffer over-read in the public key verification method.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 21 Jan 2026
- **Also known as:** GHSA-6qpj-whq8-wr7j

## What is CVE-2025-66692?

CVE-2025-66692 is a high-severity memory corruption vulnerability in n/a, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer over-read in the PublicKey::verify() method of Binance - Trust Wallet Core before commit 5668c67 allows attackers to cause a Denial of Service (DoS) via a crafted input.

Weakness: CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2025-66692?

It affects 1 product.


Products: Trustwallet Trust Wallet Core.

## How do I fix CVE-2025-66692?

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

## Is CVE-2025-66692 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66692 and fix it if it is affected.

What it is: CVE-2025-66692 is a high-severity memory corruption vulnerability in n/a, published on 20 Jan 2026. 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-2025-66692 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-2025-66692/ (Markdown: https://insights.sbomify.com/CVE-2025-66692/index.md)
```

## Sources

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

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