Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
SharpCompress versions before 0.29 are affected. When ExtractFullPath is enabled, a crafted archive can cause files to be created in a sibling directory whose name starts with the destination directory's name, because the destination path is not required to end with a slash during the containment check. The impact is limited to file creation, and its reach depends on how the application uses extraction. Upgrade to SharpCompress 0.29 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.012, the 68th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:22 UTC First seen by agentprime
- 31 Oct 2026, 15:22 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-jp7f-grcv-6mjf
- OSV: GHSA-jp7f-grcv-6mjf
- github.com/adamhathcock/sharpcompress/security/advisories/GHSA-jp7f-grcv-6mjf
- nvd.nist.gov/vuln/detail/CVE-2021-39208
- github.com/adamhathcock/sharpcompress/pull/614
- github.com/adamhathcock/sharpcompress/commit/ea5c8dc06314c7a5068e7901c51a625224d2b288
- github.com/adamhathcock/sharpcompress
- github.com/adamhathcock/sharpcompress/releases/tag/0.29.0