Winny is a narrowly scoped vendor with a focused product line centered on a single offering, representing a modest footprint in the vulnerability landscape. The observed disclosures cluster around input-validation weaknesses, reflecting the application's exposure to untrusted data streams; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Winny over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2010-2361HIGH Winny 2.0b7.1 and earlier does not properly process BBS information, which has unspecified impact and remote attack vectors that might lead to use of the product's host for DDoS at | Aug 25, 2010 | 10.0 | 28 | NO | NO |
CVE-2010-2362HIGH Winny 2.0b7.1 and earlier does not properly process node information, which has unspecified impact and remote attack vectors that might lead to use of the product's host for DDoS a | Aug 25, 2010 | 10.0 | 27 | NO | NO |
CVE-2006-2007HIGH Heap-based buffer overflow in Winny 2.0 b7.1 and earlier allows remote attackers to execute arbitrary code via long strings to certain commands sent to the file transfer port. | Apr 25, 2006 | 7.5 | 27 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Winny.
Media articles that mention a CVE ID that affects a product developed by Winny — matched by CVE ID, not by vendor name.