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.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gchp-q4r4-x4ff | tar-rs incorrectly ignores PAX size headers if header size is nonzero |
Mon, 23 Mar 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:alexcrichton:tar-rs:*:*:*:*:*:rust:*:* | |
| Metrics |
cvssV3_1
|
Fri, 20 Mar 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Alexcrichton
Alexcrichton tar-rs |
|
| Vendors & Products |
Alexcrichton
Alexcrichton tar-rs |
Fri, 20 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 20 Mar 2026 07:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45. | |
| Title | tar-rs incorrectly ignores PAX size headers if header size is nonzero | |
| Weaknesses | CWE-843 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-20T15:44:15.706Z
Reserved: 2026-03-17T18:10:50.213Z
Link: CVE-2026-33055
Updated: 2026-03-20T15:44:11.127Z
Status : Analyzed
Published: 2026-03-20T07:16:13.543
Modified: 2026-03-23T15:27:16.467
Link: CVE-2026-33055
No data.
OpenCVE Enrichment
Updated: 2026-03-25T14:30:12Z
Github GHSA