{"id":"GHSA-3cv2-h65g-fgmm","revision":"1f166c3a8c014fb38f6fdc24c7c3d6dd","records":[{"revision":"1f166c3a8c014fb38f6fdc24c7c3d6dd","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-3cv2-h65g-fgmm","aliases":["RUSTSEC-2026-0145"],"title":"astral-tokio-tar has a PAX Header Desynchronization issue","description":"### Impact\n\nVersions of astral-tokio-tar prior to 0.6.2 contain a PAX header interpretation bug that allows manipulated entries to be made selectively visible or invisible during extraction with astral-tokio-tar versus other tar implementations. An attacker could use this differential to smuggle unexpected files onto a victim's filesystem.\n\n### Details\n\nWhen a tar stream contains multiple \"header\" entries prior to a file entry, astral-tokio-tar applies the PAX header (`x`) to the next entry in the stream, regardless of type. For example, a stream of `x -> L -> file` (PAX, GNU longname, file) would result in `x`'s extensions being applied to `L` rather than to `file`.\n\n[Per POSIX pax](https://pubs.opengroup.org/onlinepubs/9799919799/utilities/pax.html), this is incorrect: a PAX header always applies to a file entry, not any intermediary entries. See the \"pax Header Block\" section for the specific prescription there.\n\nAs a result of this, an attacker can contrive a tar containing a sequence of tar headers such that astral-tokio-tar applies the PAX header's size extension to the next header in sequence, effectively desynchronizing the stream and enabling astral-tokio-tar specific skippage/extraction of members. In other words, a file can be contrived to extract differently on astral-tokio-tar than on other tar parsers.\n\n### Patches\n\nVersions 0.6.2 and newer of astral-tokio-tar address this differential.\n\n### Workarounds\n\nUsers are advised to upgrade to version 0.6.1 or newer to address this advisory.\n\nThere is no workaround other than upgrading. Users should experience no breaking changes as a result of the upgrade.\n\n### Resources\n\n- GHSA-j5gw-2vrg-8fgx is a similar PAX desynchronization bug\n- GHSA-fp55-jw48-c537 is another similar PAX desynchronization bug","state":0,"publishedAt":"2026-05-29T19:08:23+00:00","modifiedAt":"2026-05-29T19:15:14.5744568+00:00","affected":[{"ecosystem":"crates.io","name":"astral-tokio-tar","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"0.6.2"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-3cv2-h65g-fgmm","https://github.com/astral-sh/tokio-tar","https://rustsec.org/advisories/RUSTSEC-2026-0145.html"],"sourceUrl":"https://github.com/advisories/GHSA-3cv2-h65g-fgmm","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-3cv2-h65g-fgmm","identifiers":["GHSA-3cv2-h65g-fgmm","RUSTSEC-2026-0145"]},"retained":false,"historicalAffected":[]}],"coverage":[]}