CVE-2026-103060 Affecting rebar3 package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN13-REBAR3-21176502
- published18 Oct 2026
- disclosed12 Oct 2026
Introduced: 12 Oct 2026
NewCVE-2026-103060 (opens in a new tab)How to fix?
There is no fixed version for Debian:13 rebar3.
NVD Description
Note: Versions mentioned in the description apply only to the upstream rebar3 package and not the rebar3 package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2026-103060
- https://cna.erlef.org/cves/CVE-2026-103060.html
- https://github.com/erlang/rebar3/commit/56b7d88975aa8da6446857cfd92de0825024bf63
- https://github.com/erlang/rebar3/commit/e35282b26e499b1d9e8f30bba9dccd71cd8b02ba
- https://osv.dev/vulnerability/EEF-CVE-2026-103060
- https://github.com/erlang/rebar3/security/advisories/GHSA-6ggr-r7mh-2mv8