Path traversal in Gleam via unvalidated package application names
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Gleam | Gleam | unaffected |
|
|||||||||||||||||||||||||||||||||
| Gleam | Gleam | unaffected |
|
|||||||||||||||||||||||||||||||||
| Gleam | Gleam | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Gleam | Gleam |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Gleam | Gleam |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Gleam | Gleam |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Gleam-lang | Gleam |
|
Vendor Solution
Upgrade Gleam to 1.19.2 or later. Gleam then rejects a hex.pm release whose OTP application name, or the application name it gives a dependency, isn't a lowercase letter followed by lowercase letters, digits and _.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.398% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gleam
Gleam gleam |
|
| Vendors & Products |
Gleam
Gleam gleam |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in gleam-lang gleam allows a malicious package publisher to delete a directory outside the project's build directory when a developer builds a project. A Hex package release's metadata carries an app field with the release's OTP application name. Gleam reads this field from the hex.pm release API when it downloads dependencies and uses it as the package's build directory name without validating it (hex_manifest_package in compiler-cli/src/dependencies.rs, ProjectPaths::build_directory_for_package). When a dependency fails to compile, Gleam deletes that directory with remove_dir_all. 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 or an absolute path. When a project depends on such a release directly or transitively and the release fails to compile, gleam build, gleam check, gleam run, gleam test or gleam export deletes the directory the name resolves to. For a pure Gleam package no publisher code runs. This issue affects gleam: from 0.32.4 before 1.19.2. | |
| Title | Path traversal in Gleam via unvalidated package application names | |
| First Time appeared |
Gleam-lang
Gleam-lang gleam |
|
| Weaknesses | CWE-22 | |
| CPEs | cpe:2.3:a:gleam-lang:gleam:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Gleam-lang
Gleam-lang gleam |
|
| References |
|
|
| Metrics |
cvssV4_0
|