Path traversal in github.com/ipfs/go-ipfs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

EPSS

• CVE-2020-26279: 1.70% estimated exploitation activity in the next 30 days; percentile 77.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact It is currently possible for path traversal to occur with DAGs containing relative paths during retrieval. This can cause files to be overwritten, or written to incorrect output directories. The issue can only occur when ipfs get is done on an affected DAG. 1. The only affected command is ipfs get. 2. The gateway is not affected. Patches Traversal fix patched in https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227 tar-utils patch applied to go-ipfs via https://github.com/ipfs/go-ipfs/commit/b7ddba7fe47dee5b1760b8ffe897908417e577b2 Workarounds Upgrade to go-ipfs 0.8 or later. References Binaries for the patched versions of go-ipfs are available on the IPFS distributions site, https://dist.ipfs.io/go-ipfs For more information If you have any questions or comments about this advisory: Open an issue in go-ipfs Email us at security@ipfs.io

Published by the source

23 Jun 2021, 17:27 UTC

Last modified by the source

9 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-27pv-q55r-222g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-26279

Advisory: Path traversal in github.com/ipfs/go-ipfs
IDs: CVE-2020-26279, GHSA-27pv-q55r-222g
Record: https://patchnext.com/advisories/cve-2020-26279 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ipfs/go-ipfs 0.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ipfs/go-ipfs: affected < 0.8.0; fixed in 0.8.0

## Suggested inspection (read-only)
- Go github.com/ipfs/go-ipfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ipfs/go-ipfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-27pv-q55r-222g (GitHub-reviewed advisory GHSA-27pv-q55r-222g lists affected ranges: Go github.com/ipfs/go-ipfs >=0 <0.8.0)

Commands are suggestions: review each one before running it.