CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NHigh (8.1) in astral-sh tokio-tar. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in astral-tokio-tar 0.5.6.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:Nastral-tokio-tar (crates.io): fixed in 0.5.6Explain CVE-2025-62518 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-62518?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-62518?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-62518 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| astral-sh tokio-tar | < 0.5.6 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-j5gw-2vrg-8fgx | crates.io | astral-tokio-tar | <0.5.6 | 0.5.6 |
| GHSA-j5gw-2vrg-8fgx | crates.io | tokio-tar | <=0.3.1 | no fix published |
| RUSTSEC-2025-0110 | crates.io | astral-tokio-tar | >=0.0.0-0 <0.5.6 | 0.5.6 |
| RUSTSEC-2025-0111 | crates.io | tokio-tar | >=0.0.0-0 | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | rust-astral-tokio-tar | no fix listed | DEBIAN-CVE-2025-62518 |
| Debian | 14 | rust-astral-tokio-tar | 0.5.6-1 | DEBIAN-CVE-2025-62518 |
| Ubuntu | 25.10, 26.04:LTS | rust-astral-tokio-tar | no fix listed | UBUNTU-CVE-2025-62518 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | python-uv | 0.7.18-160000.3.1 | SUSE-SU-2026:20077-1 |
| openSUSE | Leap 16.0 | python-uv | 0.7.18-160000.3.1 | openSUSE-SU-2026:20026-1 |
| openSUSE | Tumbleweed | python-uv | 0.9.5-1.1 | openSUSE-SU-2025:15658-1 |
| openSUSE | Tumbleweed | zed | 1.24.2-1.1 | openSUSE-SU-2026:12355-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Important.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-monitor-rhel9 | Not affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-operator-bundle | Not affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-podvm-builder-rhel9 | Affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-podvm-payload-rhel9 | Affected | |
| Confidential Compute Attestation | openshift-sandboxed-containers/osc-rhel9-operator | Affected | |
| Red Hat Enterprise Linux 10 | trustee-guest-components | Not affected | |
| Red Hat Enterprise Linux 9 | trustee-guest-components | Not affected | |
| Red Hat OpenShift Container Platform 4 | kata-containers | Will not fix |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-62518.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.