rebar3 — security advisory
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in erlang rebar3 allows a malicious package publisher to delete a directory outside the project's _build directory and extract package files into it when a developer fetches dependencies. A package release's dependencies in a Hex registry carry an app field that names the dependency's OTP application. rebar3 uses this field as the dependency's name without validating it (rebar_packages:parse_deps/1) and builds the dependency's directory from that name (rebar_app_utils:dep_to_app/7). rebar_fetch:download_source_online/2 deletes that directory with rm -rf and moves the fetched package into it. hex.pm didn't restrict the field to a directory name before 2026-10-12, so a publisher could set it to a value such as ../../../../target. When a project depends on such a release directly or transitively, rebar3 get-deps deletes the directory the name resolves to and writes the dependency's files there. This happens before the dependency's own rebar.config.script is evaluated, and get-deps compiles nothing. This issue affects rebar3: from 3.7.0-rc1 before 3.27.2.
- Products
- rebar3
- Affected versions
- 3.19.0-1, 3.23.0-1, 3.23.0-2, 3.23.0-3, 3.24.0-1, 3.25.1-1, 3.26.0-1, 3.27.0-1, 3.27.0-2, 3.27.0-3, 3.27.0-4, 3.27.0-5, 3.27.0-6, 3.27.3-1
- Fixed versions
- 3.27.3-1
- CVEs
- CVE-2026-103060
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 23:11 UTC · Revision 1
Source evidence
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in erlang rebar3 allows a malicious package publisher to delete a directory outside the project's _build directory and extract package files into it when a developer fetches dependencies. A package release's dependencies in a Hex registry carry an app field that names the dependency's OTP application. rebar3 uses this field as the dependency's name without validating it (rebar_packages:parse_deps/1) and builds the dependency's directory from that name (rebar_app_utils:dep_to_app/7). rebar_fetch:download_source_online/2 deletes that directory with rm -rf and moves the fetched package into it. hex.pm didn't restrict the field to a directory name before 2026-10-12, so a publisher could set it to a value such as ../../../../target. When a project depends on such a release directly or transitively, rebar3 get-deps deletes the directory the name resolves to and writes the dependency's files there. This happens before the dependency's own rebar.config.script is evaluated, and get-deps compiles nothing. This issue affects rebar3: from 3.7.0-rc1 before 3.27.2.
osv:DEBIAN-CVE-2026-103060
rebar3
Fixed versions: Not specified
rebar3
Fixed versions: Not specified
rebar3
Fixed versions: 3.27.3-1
Complete source record
{
"id": "f26d12904ab982a4db4a8f13334b003417ed6d2cf387c4fdc14c26522d8bfbfb",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-103060",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-103060",
"summary": "Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in erlang rebar3 allows a malicious package publisher to delete a directory outside the project's _build directory and extract package files into it when a developer fetches dependencies. A package release's dependencies in a Hex registry carry an app field that names the dependency's OTP application. rebar3 uses this field as the dependency's name without validating it (rebar_packages:parse_deps/1) and builds the dependency's directory from that name (rebar_app_utils:dep_to_app/7). rebar_fetch:download_source_online/2 deletes that directory with rm -rf and moves the fetched package into it. hex.pm didn't restrict the field to a directory name before 2026-10-12, so a publisher could set it to a value such as ../../../../target. When a project depends on such a release directly or transitively, rebar3 get-deps deletes the directory the name resolves to and writes the dependency's files there. This happens before the dependency's own rebar.config.script is evaluated, and get-deps compiles nothing. This issue affects rebar3: from 3.7.0-rc1 before 3.27.2.",
"evidence": "osv:DEBIAN-CVE-2026-103060",
"products": [
{
"name": {
"value": "rebar3",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "3.19.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "3.23.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "3.23.0-2",
"evidence": "/affected/0/versions"
},
{
"value": "3.23.0-3",
"evidence": "/affected/0/versions"
},
{
"value": "3.24.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "3.25.1-1",
"evidence": "/affected/0/versions"
},
{
"value": "3.26.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "3.27.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "3.27.0-2",
"evidence": "/affected/0/versions"
},
{
"value": "3.27.0-3",
"evidence": "/affected/0/versions"
},
{
"value": "3.27.0-4",
"evidence": "/affected/0/versions"
},
{
"value": "3.27.0-5",
"evidence": "/affected/0/versions"
},
{
"value": "3.27.0-6",
"evidence": "/affected/0/versions"
},
{
"value": "3.27.3-1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "rebar3",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "3.24.0-1",
"evidence": "/affected/1/versions"
},
{
"value": "3.25.1-1",
"evidence": "/affected/1/versions"
},
{
"value": "3.26.0-1",
"evidence": "/affected/1/versions"
},
{
"value": "3.27.0-1",
"evidence": "/affected/1/versions"
},
{
"value": "3.27.0-2",
"evidence": "/affected/1/versions"
},
{
"value": "3.27.0-3",
"evidence": "/affected/1/versions"
},
{
"value": "3.27.0-4",
"evidence": "/affected/1/versions"
},
{
"value": "3.27.0-5",
"evidence": "/affected/1/versions"
},
{
"value": "3.27.0-6",
"evidence": "/affected/1/versions"
},
{
"value": "3.27.3-1",
"evidence": "/affected/1/versions"
}
]
},
{
"name": {
"value": "rebar3",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.27.3-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": [
{
"value": "3.24.0-1",
"evidence": "/affected/2/versions"
},
{
"value": "3.25.1-1",
"evidence": "/affected/2/versions"
},
{
"value": "3.26.0-1",
"evidence": "/affected/2/versions"
},
{
"value": "3.27.0-1",
"evidence": "/affected/2/versions"
},
{
"value": "3.27.0-2",
"evidence": "/affected/2/versions"
},
{
"value": "3.27.0-3",
"evidence": "/affected/2/versions"
},
{
"value": "3.27.0-4",
"evidence": "/affected/2/versions"
},
{
"value": "3.27.0-5",
"evidence": "/affected/2/versions"
},
{
"value": "3.27.0-6",
"evidence": "/affected/2/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "DEBIAN-CVE-2026-103060",
"aliases": [
"DEBIAN-CVE-2026-103060"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "rebar3",
"purl": "pkg:deb/debian/rebar3?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"3.19.0-1",
"3.23.0-1",
"3.23.0-2",
"3.23.0-3",
"3.24.0-1",
"3.25.1-1",
"3.26.0-1",
"3.27.0-1",
"3.27.0-2",
"3.27.0-3",
"3.27.0-4",
"3.27.0-5",
"3.27.0-6",
"3.27.3-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-103060.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "rebar3",
"purl": "pkg:deb/debian/rebar3?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"versions": [
"3.24.0-1",
"3.25.1-1",
"3.26.0-1",
"3.27.0-1",
"3.27.0-2",
"3.27.0-3",
"3.27.0-4",
"3.27.0-5",
"3.27.0-6",
"3.27.3-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-103060.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "3.27.3-1"
}
]
}
],
"package": {
"name": "rebar3",
"purl": "pkg:deb/debian/rebar3?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"3.24.0-1",
"3.25.1-1",
"3.26.0-1",
"3.27.0-1",
"3.27.0-2",
"3.27.0-3",
"3.27.0-4",
"3.27.0-5",
"3.27.0-6"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-103060.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-23T17:47:36.660196601Z",
"provider": "osv",
"upstream": [
"CVE-2026-103060"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-103060"
]
},
"related_cves": [
{
"value": "CVE-2026-103060",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 417917,
"published_at": "2026-10-12T16:17:00.873+00:00"
}