Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2025-66692 is a high-severity Buffer Over-read (CWE-126) vulnerability in Trustwallet Trust Wallet Core. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-66692 is a buffer over-read vulnerability (CWE-126) in the PublicKey::verify() method of Binance - Trust Wallet Core prior to commit 5668c67. This flaw allows attackers to trigger a Denial of Service (DoS) condition through a crafted input. The vulnerability carries a CVSS v3.1 base score of 7.5, rated as High severity with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating network accessibility, low attack complexity, no privileges or user interaction required, and high impact on availability.
Remote, unauthenticated attackers can exploit this vulnerability by supplying malicious input to the affected PublicKey::verify() function, causing a buffer over-read that crashes the application and results in a DoS. No privileges, user interaction, or special access are needed, making it feasible for attackers targeting systems or applications integrating vulnerable versions of Trust Wallet Core.
Mitigation is addressed in the patching commit at https://github.com/trustwallet/wallet-core/commit/5668c67, which users should apply to versions before 5668c67. Further technical details are provided in the advisory gist at https://gist.github.com/inkman97/b791189338f73b758c31a7db3cd50c2d. The CVE was published on 2026-01-20T21:16:04.437.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3336
Vulnerability Data
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, bounds checking tests) directly finds buffer over-read flaws.
Engineering principles such as memory-safe design and bounds-checked abstractions structurally stop introduction of out-of-bounds reads.
Process isolation limits the blast radius of an over-read to the compromised domain.
Input validation enforces length and index constraints that prevent many externally triggered over-reads.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly prevent introduction of buffer over-read weaknesses.
Vulnerability identification processes can discover buffer over-read flaws via scanning or review.
Patching or replacing vulnerable software removes known instances of buffer over-read bugs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect buffer over-reads before release.
Secure SDLC mandates input validation and bounds checking that can prevent buffer over-reads.
Application security requirements can specify buffer-size and bounds-checking rules.
Secure architecture principles include memory-safety and bounds-checking design choices.
Secure coding standards directly require bounds-checked buffer access, mitigating over-reads.