Ackites KillWxapkg wxapkg File Decompression resource consumption
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Passive
- Attack complexity
- High
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · Low
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-400.
Summary
A vulnerability was found in Ackites KillWxapkg up to 2.4.1. It has been rated as problematic. This issue affects some unknown processing of the component wxapkg File Decompression Handler. The manipulation leads to resource consumption. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Ackites | KillWxapkg | 2.4.0; 2.4.1 | — | No fix listed | CNA |
| — | github.com/Ackites/KillWxapkg (Go) | up to 2.4.1 | — | No fix listed | GHSA-pqqp-7cp8-vxvf |
- KillWxapkg VendorAckites Affected 2.4.0; 2.4.1 Fixed in — No fix listed CNA
- github.com/Ackites/KillWxapkg (Go) Vendor— Affected up to 2.4.1 Fixed in — No fix listed GHSA-pqqp-7cp8-vxvf
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-5031
- 2026-10-03 Alias added: GHSA-pqqp-7cp8-vxvf
References
More Ackites vulnerabilities
- TI-2025-04509 Ackites KillWxapkg wxapkg File Parser unpack.go processFile os command injection CVSS 4.0LOW 2.3
Sources
- CVE-2025-5031 · CVE Program
- CVE-2025-5031 · NVD
- FIRST EPSS
- GHSA-pqqp-7cp8-vxvf · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences