CVE-2020-26312
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.
Read full descriptionShow less
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 has permissions to read. As of time of publication, no patch for this issue is available.
CVSS
- Version: 3.1
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Base score: 8.1
Exploitation probability (EPSS)
- Probability of exploitation in the next 30 days: 0.44%
- Percentile among all scored CVEs: 36
- Score date: 10/7/2026
EPSS (Exploit Prediction Scoring System, FIRST) estimates how likely a vulnerability is to be exploited in the wild within 30 days. It complements CVSS (impact) and CISA KEV (confirmed exploitation).
Affected technologies (1)
⚠ AI-inferred from the description — NVD hasn't analyzed this CVE yet, these aren't verified CPEs.
CWEs
- CWE-125, CWE-787
References
Raw JSON (NVD)
Show
{
"id": "CVE-2020-26312",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2020-26312",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"version": "2.0.3",
"timestamp": "2024-05-15T15:03:53.759790Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "security-advisories@github.com",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 8.1,
"attackVector": "NETWORK",
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"integrityImpact": "HIGH",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "NONE",
"privilegesRequired": "LOW",
"confidentialityImpact": "HIGH"
},
"impactScore": 5.2,
"exploitabilityScore": 2.8
}
]
},
"affected": [
{
"source": "security-advisories@github.com",
"affectedData": [
{
"repo": "https://github.com/dotmesh-io/dotmesh",
"vendor": "dotmesh-io",
"product": "dotmesh",
"versions": [
{
"status": "affected",
"version": "0",
"versionType": "custom",
"lessThanOrEqual": "0.8.1"
}
],
"packageName": "dotmesh",
"defaultStatus": "unaffected"
}
]
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"affectedData": [
{
"cpes": [
"cpe:2.3:a:dotmesh-io:dotmesh:*:*:*:*:*:*:*:*"
],
"vendor": "dotmesh-io",
"product": "dotmesh",
"versions": [
{
"status": "affected",
"version": "0",
"versionType": "custom",
"lessThanOrEqual": "0.8.1"
}
],
"defaultStatus": "unknown"
}
]
}
],
"published": "2024-05-14T21:15:10.587",
"references": [
{
"url": "https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255",
"source": "security-advisories@github.com"
},
{
"url": "https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/",
"source": "security-advisories@github.com"
},
{
"url": "https://github.com/dotmesh-io/dotmesh/blob/master/pkg/archiver/tar.go#L255",
"source": "af854a3a-2127-422b-91ae-364da2661108"
},
{
"url": "https://securitylab.github.com/advisories/GHSL-2020-254-zipslip-dotmesh/",
"source": "af854a3a-2127-422b-91ae-364da2661108"
}
],
"vulnStatus": "Deferred",
"weaknesses": [
{
"type": "Secondary",
"source": "security-advisories@github.com",
"description": [
{
"lang": "en",
"value": "CWE-125"
},
{
"lang": "en",
"value": "CWE-787"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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 \nenable attackers to read and/or write to arbitrary locations outside the\n 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 has permissions to read. As of time of publication, no patch for this issue is available.\n"
},
{
"lang": "es",
"value": "Dotmesh es una interfaz de línea de comandos similar a git para capturar, organizar y compartir estados de aplicaciones. En las versiones 0.8.1 y anteriores, el manejo inseguro de enlaces simbólicos en una rutina de descompresión puede permitir a los atacantes leer y/o escribir en ubicaciones arbitrarias fuera de la carpeta de destino designada. La rutina `untarFile` intenta evitar la creación de enlaces simbólicos que apunten fuera del directorio al que se extrae un archivo tar. Sin embargo, un tarball malicioso que primero vincula `subdir/parent` a `..` (permitido, porque `subdir/..` se encuentra dentro de la raíz del archivo) y luego vincula `subdir/parent/escapes` a `..` da como resultado un enlace simbólico que apunta al directorio principal del tarball, contrario a los objetivos de la rutina. Este problema puede provocar la escritura arbitraria de archivos (con los mismos permisos que el programa que ejecuta la operación de descomprimir) si el atacante puede controlar el archivo comprimido. Además, si el atacante tiene acceso de lectura a los archivos descomprimidos, es posible que pueda leer archivos arbitrarios del sistema para los que el proceso principal tiene permisos de lectura. Al momento de la publicación, no hay ningún parche disponible para este problema."
}
],
"lastModified": "2026-06-17T03:08:03.413",
"sourceIdentifier": "security-advisories@github.com"
}