{"id":"CVE-2025-62518","aliases":["DEBIAN-CVE-2025-62518","EUVD-2025-35176","GHSA-j5gw-2vrg-8fgx","RUSTSEC-2025-0110","RUSTSEC-2025-0111","SUSE-SU-2026:20077-1","UBUNTU-CVE-2025-62518","openSUSE-SU-2025:15658-1","openSUSE-SU-2026:12355-1","openSUSE-SU-2026:20026-1"],"status":"published","title":"astral-tokio-tar Vulnerable to PAX Header Desynchronization","description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.","severity":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00703,"percentile":0.53757,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-843"],"published":"2025-10-21T12:00:00Z","modified":"2026-10-31T18:12:01Z","exploits":[{"source":"pocgithub","id":"edera-dev/cve-tarmageddon","title":"edera-dev/cve-tarmageddon","date":"2025-08-21","url":"https://github.com/edera-dev/cve-tarmageddon"},{"source":"pocgithub","id":"AirineiAndrei/Tarmageddon-CVE-2025-62518-","title":"AirineiAndrei/Tarmageddon-CVE-2025-62518-","date":"2026-01-19","url":"https://github.com/AirineiAndrei/Tarmageddon-CVE-2025-62518-"}],"fixes":[{"ecosystem":"crates.io","package":"astral-tokio-tar","fixed_in":["0.5.6"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:14","package":"rust-astral-tokio-tar","fixed_in":["0.5.6-1"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"python-uv","fixed_in":["0.9.5-1.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"astral-tokio-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.5.5"},{"fixed":"0.5.6"}]}]},{"source":"ghsa","ecosystem":"crates.io","package":"tokio-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.3.1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"rust-astral-tokio-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.5.2-2","0.5.5-1","0.5.6-1","0.5.6-2","0.6.0-1","0.6.1-1","0.6.2-1","0.6.4-1"]},{"source":"osv","ecosystem":"Debian:14","package":"rust-astral-tokio-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.6-1"}]}],"versions":["0.5.2-2","0.5.5-1"]},{"source":"osv","ecosystem":"crates.io","package":"astral-tokio-tar","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.5.6"}]}]},{"source":"osv","ecosystem":"crates.io","package":"tokio-tar","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.3.1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"astral-tokio-tar","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.5.6"}]}]},{"source":"osv","ecosystem":"crates.io","package":"tokio-tar","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"python-uv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.18-160000.3.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"python-uv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.18-160000.3.1"}]}],"bundled":2},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"rust-astral-tokio-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.5.1-1","0.5.2-2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"rust-astral-tokio-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.5.2-2","0.5.5-1","0.5.6-1","0.5.6-2"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"python-uv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.5-1.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"zed","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.24.2-1.1"}]}],"bundled":11},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"python-uv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.18-160000.3.1"}]}],"bundled":2}],"products":[{"vendor":"astral-sh","product":"tokio-tar"}],"references":[{"url":"https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-j5gw-2vrg-8fgx","tags":["x_refsource_CONFIRM","advisory","web","report"]},{"url":"https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9","tags":["x_refsource_MISC","advisory","web","report"]},{"url":"https://github.com/astral-sh/tokio-tar/commit/22b3f884adb7a2adf1d3a8d03469533f5cbc8318","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://edera.dev/stories/tarmageddon","tags":["x_refsource_MISC","web","report"]},{"url":"https://github.com/edera-dev/cve-tarmageddon","tags":["x_refsource_MISC","package","web","report"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2025-0110.html","tags":["web","advisory"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2025-0111.html","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-j5gw-2vrg-8fgx"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/62xxx/CVE-2025-62518.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-62518","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-62518","tags":["advisory"]},{"url":"https://github.com/astral-sh/tokio-tar","tags":["package"]},{"url":"https://crates.io/crates/astral-tokio-tar","tags":["package"]},{"url":"https://crates.io/crates/tokio-tar","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620077-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1249011","tags":["report"]},{"url":"https://bugzilla.suse.com/1252399","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-58160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-62518","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2025-62518","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-62518","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-4574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-25541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-27204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93600","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2025-62518","title":"astral-tokio-tar Vulnerable to PAX Header Desynchronization","description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.","status":"published","published":"2025-10-21T16:13:02.646Z","modified":"2025-10-22T13:23:33.408Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T14:32:54.87586Z"}],"euvd":[{"id":"EUVD-2025-35176","description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.","status":"published","published":"2025-10-21T16:13:02Z","modified":"2025-10-22T13:23:33Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T19:49:38.726368Z"}],"ghsa":[{"id":"GHSA-j5gw-2vrg-8fgx","title":"astral-tokio-tar Vulnerable to PAX Header Desynchronization","description":"## Summary\n\nVersions of `astral-tokio-tar` prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers.\n\nThis vulnerability was disclosed to multiple Rust tar parsers, all derived from the original `async-tar` fork of `tar-rs`.\n\n## Details\n\n### Vulnerability Description\n\nThe vulnerability stems from inconsistent handling of PAX extended headers versus ustar headers when determining file data boundaries. Specifically:\n\n1. **PAX header** correctly specifies the file size (e.g., `size=1048576`)\n2. **ustar header** incorrectly specifies zero size (`size=000000000000`)\n3. **tokio-tar** advances the stream position based on the ustar size (0 bytes)\n4. **Inner content** is then interpreted as legitimate outer archive entries\n\n### Attack Mechanism\n\nWhen a TAR file contains:\n\n- An outer entry with PAX `size=N` but ustar `size=0`\n- File data that begins with valid TAR header structures\n- The parser treats inner content as additional outer entries\n\nThis creates a **header/data desynchronization** where the parser's position becomes misaligned with actual file boundaries.\n\n### Root Cause\n\n```rust\n// Vulnerable: Uses ustar size instead of PAX override\nlet file_size = header.size(); // Returns 0 from ustar field\nlet next_pos = current_pos + 512 + pad_to_512(file_size); // Advances 0 bytes\n\n// Fixed: Apply PAX overrides before position calculation\nlet mut file_size = header.size();\nif let Some(pax_size) = pending_pax.get(\"size\") {\n    file_size = pax_size.parse().unwrap();\n}\nlet next_pos = current_pos + 512 + pad_to_512(file_size); // Correct advance\n\n```\n\n## Impact\n\nThe impact of this vulnerability depends on where `astral-tokio-tar` is used, and whether it is used to extract untrusted tar archives. If used to extract untrusted inputs, it may result in unexpected attacker-controlled access to the filesystem, in turn potential resulting in arbitrary code execution or credential exfiltration.\n\nSee [**GHSA-w476-p2h3-79g9**](https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9) for how this vulnerability affects `uv`, `astral-tokio-tar`'s primary downstream user. Observe that **unlike** this advisory,` uv`'s advisory is considered **low severity** due to overlap with intentional existing capabilities in source distributions. \n\n## Workarounds\n\nUsers are advised to upgrade to version 0.5.6 or newer to address this advisory.\n\nThere is no workaround other than upgrading.\n\n## Timeline\n\n| Date | Event |\n| --- | --- |\n| Aug 21, 2025 | Vulnerability discovered by Edera Security Team |\n| Aug 21, 2025 | Initial analysis and PoC confirmed |\n| Aug 22, 2025 | Maintainers notified (privately) |\n| Aug 25, 2025 | Private patch and test suite shared |\n| Oct 7, 2025 | Text freeze for GHSA |\n| Oct 21, 2025 | Coordinated public disclosure and patched releases |\n\n## Credits\n\n- **Discovered by:** Steven Noonan (Edera) and Alex Zenla (Edera)\n- **Coordinated disclosure:** Ann Wallace (Edera)","status":"published","published":"2025-10-21T15:42:51Z","modified":"2026-01-16T22:12:13Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T14:39:18.564331Z"}],"nvd":[{"id":"CVE-2025-62518","description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.","status":"published","published":"2025-10-21T17:15:40.563Z","modified":"2026-10-08T11:10:00.25Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T14:11:39.069866Z"}],"osv":[{"id":"CVE-2025-62518","title":"astral-tokio-tar Vulnerable to PAX Header Desynchronization","description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.","status":"published","published":"2025-10-21T16:13:02.646Z","modified":"2026-10-31T18:12:01.666054175Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T15:44:51.851511Z"},{"id":"DEBIAN-CVE-2025-62518","description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.","status":"published","published":"2025-10-21T17:15:40.563Z","modified":"2026-10-09T09:47:36.316180913Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:45:47.697959Z"},{"id":"GHSA-j5gw-2vrg-8fgx","title":"astral-tokio-tar Vulnerable to PAX Header Desynchronization","description":"## Summary\n\nVersions of `astral-tokio-tar` prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers.\n\nThis vulnerability was disclosed to multiple Rust tar parsers, all derived from the original `async-tar` fork of `tar-rs`.\n\n## Details\n\n### Vulnerability Description\n\nThe vulnerability stems from inconsistent handling of PAX extended headers versus ustar headers when determining file data boundaries. Specifically:\n\n1. **PAX header** correctly specifies the file size (e.g., `size=1048576`)\n2. **ustar header** incorrectly specifies zero size (`size=000000000000`)\n3. **tokio-tar** advances the stream position based on the ustar size (0 bytes)\n4. **Inner content** is then interpreted as legitimate outer archive entries\n\n### Attack Mechanism\n\nWhen a TAR file contains:\n\n- An outer entry with PAX `size=N` but ustar `size=0`\n- File data that begins with valid TAR header structures\n- The parser treats inner content as additional outer entries\n\nThis creates a **header/data desynchronization** where the parser's position becomes misaligned with actual file boundaries.\n\n### Root Cause\n\n```rust\n// Vulnerable: Uses ustar size instead of PAX override\nlet file_size = header.size(); // Returns 0 from ustar field\nlet next_pos = current_pos + 512 + pad_to_512(file_size); // Advances 0 bytes\n\n// Fixed: Apply PAX overrides before position calculation\nlet mut file_size = header.size();\nif let Some(pax_size) = pending_pax.get(\"size\") {\n    file_size = pax_size.parse().unwrap();\n}\nlet next_pos = current_pos + 512 + pad_to_512(file_size); // Correct advance\n\n```\n\n## Impact\n\nThe impact of this vulnerability depends on where `astral-tokio-tar` is used, and whether it is used to extract untrusted tar archives. If used to extract untrusted inputs, it may result in unexpected attacker-controlled access to the filesystem, in turn potential resulting in arbitrary code execution or credential exfiltration.\n\nSee [**GHSA-w476-p2h3-79g9**](https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9) for how this vulnerability affects `uv`, `astral-tokio-tar`'s primary downstream user. Observe that **unlike** this advisory,` uv`'s advisory is considered **low severity** due to overlap with intentional existing capabilities in source distributions. \n\n## Workarounds\n\nUsers are advised to upgrade to version 0.5.6 or newer to address this advisory.\n\nThere is no workaround other than upgrading.\n\n## Timeline\n\n| Date | Event |\n| --- | --- |\n| Aug 21, 2025 | Vulnerability discovered by Edera Security Team |\n| Aug 21, 2025 | Initial analysis and PoC confirmed |\n| Aug 22, 2025 | Maintainers notified (privately) |\n| Aug 25, 2025 | Private patch and test suite shared |\n| Oct 7, 2025 | Text freeze for GHSA |\n| Oct 21, 2025 | Coordinated public disclosure and patched releases |\n\n## Credits\n\n- **Discovered by:** Steven Noonan (Edera) and Alex Zenla (Edera)\n- **Coordinated disclosure:** Ann Wallace (Edera)","status":"published","published":"2025-10-21T15:42:51Z","modified":"2026-09-10T03:50:29.925592088Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T15:46:49.977351Z"},{"id":"RUSTSEC-2025-0110","title":"astral-tokio-tar Vulnerable to PAX Header Desynchronization","description":"Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing\nvulnerability that allows attackers to smuggle additional archive entries by\nexploiting inconsistent PAX/ustar header handling. When processing archives with\nPAX-extended headers containing size overrides, the parser incorrectly advances\nstream position based on ustar header size (often zero) instead of the\nPAX-specified size, causing it to interpret file content as legitimate tar\nheaders.\n\nThis vulnerability was disclosed to multiple Rust tar parsers, all derived from\nthe original async-tar fork of tar-rs.\n\nFor additional information see\n[Edera's blog post](https://edera.dev/stories/tarmageddon).","status":"published","published":"2025-10-21T12:00:00Z","modified":"2026-10-12T18:00:11.489562704Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:39.971022Z"},{"id":"UBUNTU-CVE-2025-62518","description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.","status":"published","published":"2025-10-21T17:15:00Z","modified":"2026-05-20T16:23:39.995392086Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T16:55:50.817402Z"},{"id":"openSUSE-SU-2025:15658-1","title":"python311-uv-0.9.5-1.1 on GA media","description":"These are all security issues fixed in the python311-uv-0.9.5-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-10-22T00:00:00Z","modified":"2026-03-23T04:54:03.759089Z","updated_at":"2026-11-02T16:58:37.810934Z"},{"id":"openSUSE-SU-2026:12355-1","title":"zed-1.24.2-1.1 on GA media","description":"These are all security issues fixed in the zed-1.24.2-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-10-29T00:00:00Z","modified":"2026-10-31T18:00:05.930167365Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"openSUSE-SU-2026:20026-1","title":"Security update for python-uv","description":"This update for python-uv fixes the following issues:\n\n- CVE-2025-62518: astral-tokio-tar: Fixed boundary parsing issue\n  allowing attackers to smuggle additional archive entries\n  (bsc#1252399)\n- CVE-2025-58160: tracing-subscriber: Fixed log pollution (bsc#1249011)\n","status":"published","published":"2026-01-13T12:48:04Z","modified":"2026-03-23T04:54:41.031773Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"RUSTSEC-2025-0111","title":"`tokio-tar` parses PAX extended headers incorrectly, allows file smuggling","description":"The archive reader incorrectly handles PAX extended headers, when the ustar\nheader incorrectly specifies zero size (`size=000000000000`), while a PAX\nheader specifies a non-zero size, `tokio-tar::Archive` is going to read the\nfile content as tar entry header.\n\nThis can be used by a tar file to present different content to `tokio-tar`\ncompared to other tar reader implementations.\n\nThis bug is also known as `CVE-2025-62518` and `GHSA-j5gw-2vrg-8fgx`, as those\ncrates share a common ancestor codebase.\n\nThe `tokio-tar` crate is archived and no longer maintained, we recommend you\nswitch to an alternative crate such as:\n- [`astral-tokio-tar`](https://crates.io/crates/astral-tokio-tar)","status":"published","published":"2025-10-21T12:00:00Z","modified":"2026-02-04T02:35:07.255927Z","updated_at":"2026-11-02T15:53:39.971022Z"},{"id":"SUSE-SU-2026:20077-1","title":"Security update for python-uv","description":"This update for python-uv fixes the following issues:\n\n- CVE-2025-62518: astral-tokio-tar: Fixed boundary parsing issue\n  allowing attackers to smuggle additional archive entries\n  (bsc#1252399)\n- CVE-2025-58160: tracing-subscriber: Fixed log pollution (bsc#1249011)\n","status":"published","published":"2026-01-13T12:49:17Z","modified":"2026-03-23T04:52:33.781413Z","updated_at":"2026-11-02T15:54:01.610851Z"}]}}