CVE-2026-32766Network attack vector

Archive interpretation conflict via discarded PAX errors

Published Mar 20, 2026 · Updated Mar 20, 2026

Interpretation conflict in Astral astral-tokio-tar 0.5.6 and earlier allows remote attackers to create divergent archive views via malformed PAX extensions. EntryFields::path_bytes and link_name_bytes discarded PAX parsing errors with filter_map, silently falling back to base header values instead of rejecting the archive. Exploitation requires a second tar parser that accepts the malformed extension and assigns it different semantics, limiting the result to context-dependent integrity impact in a multi-parser workflow.

CVSS severity5.3
Medium
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Interpretation conflict in Astral astral-tokio-tar 0.5.6 and earlier allows remote attackers to create divergent archive views via malformed PAX extensions. EntryFields::path_bytes and link_name_bytes discarded PAX parsing errors with filter_map, silently falling back to base header values instead of rejecting the archive. Exploitation requires a second tar parser that accepts the malformed extension and assigns it different semantics, limiting the result to context-dependent integrity impact in a multi-parser workflow.

The record

CVE
CVE-2026-32766
Published
Mar 20, 2026
Updated
Mar 20, 2026
Vendor
Astral
Product
astral-tokio-tar
Classifications
CWE-436, CWE-20
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.6.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Astral · astral-tokio-tarversion=< 0.6.0

Published CVSS scores

1.7GitHub, Inc.CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-436Interpretation Conflict
CWE-20Improper Input Validation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo