Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 07 Nov 2025 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 04 Nov 2025 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 03 Nov 2025 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 30 Oct 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Thu, 30 Oct 2025 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Golang
Golang archive |
|
| Vendors & Products |
Golang
Golang archive |
Wed, 29 Oct 2025 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Unbounded allocation when parsing GNU sparse map in archive/tar | |
| References |
|
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2025-11-04T21:13:32.834Z
Reserved: 2025-08-27T14:50:58.691Z
Link: CVE-2025-58183
Updated: 2025-11-04T21:13:32.834Z
Status : Deferred
Published: 2025-10-29T23:16:19.357
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-58183
OpenCVE Enrichment
Updated: 2025-10-30T14:37:46Z