CVE-2025-66692: High severity Binance Trust Wallet Core vulnerability

Published Jan 20, 2026
·
Updated

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.

Affected Software

2 affected components
Binance Trust Wallet Core<5668c67
Trustwallet Trust Wallet Core<4.4.0

Event History

Jan 20, 2026
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·09:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-66692?

CVE-2025-66692 has a severity rating that indicates it can lead to Denial of Service (DoS) attacks.

2

How do I fix CVE-2025-66692?

To fix CVE-2025-66692, update your Binance Trust Wallet Core to a version after commit 5668c67.

3

What causes CVE-2025-66692?

CVE-2025-66692 is caused by a buffer over-read in the PublicKey::verify() method.

4

Which versions of Binance Trust Wallet Core are affected by CVE-2025-66692?

Binance Trust Wallet Core versions before commit 5668c67 are affected by CVE-2025-66692.

5

What is the impact of CVE-2025-66692?

The impact of CVE-2025-66692 is the potential for Denial of Service (DoS) when processing crafted input.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203