dotmesh arbitrary file read and/or write

Exploitation

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

CVSS

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

EPSS

• CVE-2020-26312: 0.44% estimated exploitation activity in the next 30 days; percentile 38.40 (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.

Dotmesh is a git-like command-line interface for capturing, organizing and sharing application states. In versions 0.8.1 and prior, the unsafe handling of symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations outside the designated target folder. The routine untarFile attempts to guard against creating symbolic links that point outside the directory a tar archive is extracted to. However, a malicious tarball first linking subdir/parent to .. (allowed, because subdir/.. falls within the archive root) and then linking subdir/parent/escapes to .. results in a symbolic link pointing to the tarball’s parent directory, contrary to the routine’s goals. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, they may be able to read arbitrary system files the parent process…

Published by the source

14 May 2024, 21:34 UTC

Last modified by the source

14 May 2024, 22:32 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hf54-fq2m-p9v6

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

# Patch Next advisory brief: CVE-2020-26312

Advisory: dotmesh arbitrary file read and/or write
IDs: CVE-2020-26312, GHSA-hf54-fq2m-p9v6
Record: https://patchnext.com/advisories/cve-2020-26312 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dotmesh-io/dotmesh: affected <= 0.8.1

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dotmesh-io/dotmesh.
- 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-hf54-fq2m-p9v6 (GitHub-reviewed advisory GHSA-hf54-fq2m-p9v6 lists affected ranges: Go github.com/dotmesh-io/dotmesh >=0 <=0.8.1)

Commands are suggestions: review each one before running it.