Relative path traversal in the log export commands in AWS ParallelCluster CLI
- Exploited
- No known exploitation
- Fix
- Fixed in 3.16.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.16.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The AWS ParallelCluster CLI's export-cluster-logs and export-image-logs commands contain a path traversal flaw that lets a user with low-privilege login and write access to the log export S3 bucket write files outside the intended export directory on the machine running the command. This requires a user to take an action, such as running the affected command, and the attacker can then create files with attacker-chosen names and content, using the privileges of the person running the command.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The export-cluster-logs and export-image-logs commands in the AWS ParallelCluster CLI before version 3.16.0 contain a relative path traversal issue. An authenticated remote user with write access to the log export Amazon S3 bucket could use a crafted S3 object key to write files outside the intended export directory on the machine running the command. The written files would have names and content controlled by a third party, and would be created with the privileges of the user running the command.
To remediate this issue, users should upgrade to version 3.16.0 or later.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.4/10CVSS 6.4
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.16.0.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- AWS aws-parallelcluster
From 3.0.0 · fixed in 3.16.0
Evidence 3
- Advisory
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124033
Is CVE-2026-124033 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-124033?
aws-parallelcluster: from 3.0.0 before 3.16.0.Source: cve.now feed data
How do I fix CVE-2026-124033?
Upgrade to a fixed version: 3.16.0.Source: cve.now feed data