CVE-2026-32685: Path Traversal in gleam docs build via documentation.pages Allows Arbitrary File Read and Write
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: Gleam Gleam 1.17.0, 81570611906b6b0039c948037094d09a68700f3a, v1.17.0-elixir.
Low priority for now. Upgrade to Gleam Gleam 1.17.0, 81570611906b6b0039c948037094d09a68700f3a, v1.17.0-elixir or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Path traversal vulnerability in Gleam's handling of custom documentation pages allows arbitrary file read and file write outside the intended documentation output directory. The documentation.pages entries from gleam.toml are incorporated into filesystem paths without sufficient validation or confinement to the intended project and documentation output directories. The documentation.pages[].path field can be used to write generated documentation files outside the intended build/dev/docs/<package>/ output directory. The documentation.pages[].source field can be used to read files outside the project directory and embed their contents into generated documentation output. An attacker who can convince a victim to run gleam docs build on an untrusted project, or with untrusted gleam.toml content, can cause local files readable by the victim to be included in generated documentation artifacts, and can cause generated documentation files to be written outside the intended docs output directory. This issue affects Gleam from 1.16.0 until 1.17.0.
- Published
- Jun 2, 2026
- Updated
- Oct 6, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-22
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · EEF
- 4.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.
Gleam Gleam
- 1.16.0 and later · before 1.17.0affected · semver
- 1.16.0 and later · before 1.17.0affected · semver
- 61ed8deb6572b5591ad17d6302c1a38607522f16 and later · before 81570611906b6b0039c948037094d09a68700f3aaffected · git
- v1.16.0-elixir and later · before v1.17.0-elixiraffected · other
- v1.16.0-erlang and later · before v1.17.0-erlangaffected · other
- v1.16.0-node and later · before v1.17.0-nodeaffected · other
- v1.16.0-node-slim and later · before v1.17.0-node-slimaffected · other
- v1.16.0-elixir-slim and later · before v1.17.0-elixir-slimaffected · other
- v1.16.0-erlang-slim and later · before v1.17.0-erlang-slimaffected · other
- v1.16.0-erlang-alpine and later · before v1.17.0-erlang-alpineaffected · other
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 16.0 | gleam | before 1.17.0-bp160.1.1 | 1.17.0-bp160.1.1 |
| openSUSE:Tumbleweed | gleam | before 1.17.0-1.1 | 1.17.0-1.1 |
Same product
gleam: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-103061Path traversal in Gleam via unvalidated package application names23Monitor
- CVE-2026-43965Path Traversal in build/packages/packages.toml Allows Arbitrary Directory Deletion22Monitor
- CVE-2026-42795Symlink Following in Hex Package Export Allows Embedding Files Outside Project Root20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Gleam Gleam | 1.17.0 | Vendor (CNA) |
| Gleam Gleam | 81570611906b6b0039c948037094d09a68700f3a | Vendor (CNA) |
| Gleam Gleam | v1.17.0-elixir | Vendor (CNA) |
| Gleam Gleam | v1.17.0-elixir-alpine | Vendor (CNA) |
| Gleam Gleam | v1.17.0-elixir-slim | Vendor (CNA) |
| Gleam Gleam | v1.17.0-erlang | Vendor (CNA) |
| Gleam Gleam | v1.17.0-erlang-alpine | Vendor (CNA) |
| Gleam Gleam | v1.17.0-erlang-slim | Vendor (CNA) |
| Gleam Gleam | v1.17.0-node | Vendor (CNA) |
| Gleam Gleam | v1.17.0-node-alpine | Vendor (CNA) |
| Gleam Gleam | v1.17.0-node-slim | Vendor (CNA) |
| Gleam Gleam | v1.17.0-scratch | Vendor (CNA) |
| opensuse:gleam | 1.17.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- evipepotafinder
- Louis Pilfoldremediation reviewer
- Jonatan Männchen / EEFanalyst
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-103061132 days apartPath traversal in Gleam via unvalidated package application names23Monitor
- CVE-2026-439650 days apartPath Traversal in build/packages/packages.toml Allows Arbitrary Directory Deletion22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/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
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.