Application crash via registration name buffer overflow
Published Feb 12, 2026 · Updated Feb 12, 2026
Buffer overflow in the registration dialog of Nsasoft Product Key Explorer 4.2.0.0 allows local attackers to crash the application. The Name field accepts a 258-character repeated-byte string without enforcing its input boundary, corrupting memory when the registration form is submitted. Pasting the payload and submitting the form is required; the demonstrated consequence is limited to termination of the application process.
Summary
What happened
Buffer overflow in the registration dialog of Nsasoft Product Key Explorer 4.2.0.0 allows local attackers to crash the application. The Name field accepts a 258-character repeated-byte string without enforcing its input boundary, corrupting memory when the registration form is submitted. Pasting the payload and submitting the form is required; the demonstrated consequence is limited to termination of the application process.
The record
- CVE
- CVE-2019-25334
- Published
- Feb 12, 2026
- Updated
- Feb 12, 2026
- Vendor
- Nsasoft
- Product
- Product Key Explorer
- Classifications
- CWE-121, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2026CVE publishedPublication date reported by the CVE source.
- Feb 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Product Key Explorer 4.2.0.0 Name Denial of Service POCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo