Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Unbounded memory allocation in Go archive/tar old GNU sparse map parsing

IdentifiersCVE-2026-32288CWE-770· Allocation of Resources Without…

CVE-2026-32288 affects Go's standard library archive/tar package. The vulnerability is in tar.Reader when parsing a maliciously crafted tar archive containing a large number of sparse regions encoded using the legacy "old GNU sparse map" format. Due to insufficient limits during sparse map parsing, tar.Reader can allocate an unbounded amount of memory while processing attacker-controlled sparse metadata. The issue is triggered during archive parsing rather than normal file extraction semantics, and specifically involves old-format GNU sparse map extension handling.

Share:
For your environment

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.

ANALYST BRIEF

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.

A remote or local attacker who can supply a crafted tar archive to a Go application using archive/tar may cause excessive memory consumption, potentially leading to process instability, resource exhaustion, or denial of service. The primary impact described in the provided content is unbounded memory allocation during parsing of malicious sparse map metadata.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, avoid processing untrusted tar archives with archive/tar, especially archives that may contain legacy old GNU sparse map entries. Apply input validation, enforce archive size and parsing resource limits externally, and isolate archive-processing workloads with memory limits to reduce denial-of-service risk.

Remediation

Patch, then assume compromise.

Upgrade to a fixed Go release that includes the archive/tar correction, specifically Go 1.26.2 or Go 1.25.9, as referenced in the provided content. The fix limits both the number of old GNU sparse map extension blocks and the total number of sparse file entries processed by tar.Reader.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
GolangGoapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.