How severe is CVE-2007-2535?

CVE-2007-2535 has a CVSS 2.0 base score of 7.8, rated high severity.

Is CVE-2007-2535 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2007-2535?

CVE-2007-2535 primarily affects Winace. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2007-2535?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2007-2535 published?

CVE-2007-2535 was published on 2007-05-09 and last updated on 2026-06-16.

CVE-2007-2535

CVE-2007-2535 is a high-severity vulnerability in Winace with a CVSS 2.0 base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.8)
EPSS exploit prediction: 3% (84th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Winace
Published: 2007-05-09
Last modified: 2026-06-16

Description

WinAce allows remote attackers to cause a denial of service (infinite loop) via a ZOO archive with a direntry structure that points to a previous file.

Frequently asked questions

What is CVE-2007-2535?: WinAce allows remote attackers to cause a denial of service (infinite loop) via a ZOO archive with a direntry structure that points to a previous file.
How severe is CVE-2007-2535?: CVE-2007-2535 has a CVSS 2.0 base score of 7.8, rated high severity.
Is CVE-2007-2535 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2007-2535?: CVE-2007-2535 primarily affects Winace. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2007-2535?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2007-2535 published?: CVE-2007-2535 was published on 2007-05-09 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:winace:winace:2.5:*:*:*:*:*:*:*
cpe:2.3:a:winace:winace:2.6.0.5:*:*:*:*:*:*:*
cpe:2.3:a:winace:winace:2.60:*:*:*:*:*:*:*

More vulnerabilities in Winace

CVE-2007-6563 — Critical (CVSS 10.0): Heap-based buffer overflow in WinAce 2.65 and earlier, and possibly other versions before 2.69, allows user-assisted…
CVE-2007-1673 — High (CVSS 7.8): unzoo.c, as used in multiple products including AMaViS 2.4.1 and earlier, allows remote attackers to cause a denial of…
CVE-2005-2856 — High (CVSS 7.5): Stack-based buffer overflow in the WinACE UNACEV2.DLL third-party compression utility before 2.6.0.0, as used in…
CVE-2005-2694 — High (CVSS 7.5): Buffer overflow in WinAce 2.6.0.5, and possibly earlier versions, allows remote attackers to execute arbitrary code via…
CVE-2006-0813 — Medium (CVSS 5.1): Heap-based buffer overflow in WinACE 2.60 allows user-assisted attackers to execute arbitrary code via a large header…

All CVEs affecting Winace →