Unknown severity · Source severity not reportedCVE-2025-58183

Unbounded allocation when parsing GNU sparse map in archive/tar

Answer in brief

CVE-2025-58183 records a Unknown severity vulnerability in Unbounded allocation when parsing GNU sparse map in archive/tar. The current sources do not mark it as known exploited. The current feed maps stdlib (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 29, 2025Updated Oct 2, 2026Source checked Oct 3, 2026First seen by HOL Oct 2, 2026Material review Oct 2, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps stdlib (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
stdlibgo	>=0 <1.24.8 >=1.25.0 <1.25.2	1.24.8, 1.25.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for stdlib.
Review the reported fix. Update stdlib to 1.24.8 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 29, 2025
Evidence: source:osv:source_dates:source-dates:record
Source modified
Oct 2, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Oct 2, 2026

Sources and claim methodology

Upstream source description

tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations.

Quoted source text, attributed separately from HOL analysis.

gitea-runner: workflow container.options passes host namespaces and capability flags to job container when privileged mode is disabledSame go ecosystem