Denial of Service in Go archive/zip filename indexing
CVE-2025-61728 affects Go's standard library package archive/zip. The vulnerability is caused by a super-linear file name indexing algorithm used to build the archive's internal filename index, which is triggered the first time a file in a ZIP archive is opened. When processing a maliciously constructed ZIP archive with attacker-controlled entry names, archive/zip can spend excessive CPU time building this index. The issue is described by the Go project as a denial-of-service condition when parsing or consuming arbitrary ZIP archives.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Denial-of-service (CPU exhaustion) in Go's archive/zip due to super-linear filename indexing when opening files in ZIP archives, enabling crafted ZIPs to consume disproportionate CPU.
A denial-of-service vulnerability in Go’s standard library archive/zip where super-linear filename indexing can be abused with crafted ZIP archives to cause excessive resource consumption.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.