CVE-2026-124033AWS aws-parallelcluster relative path traversal
CVE-2026-124033 is a relative path traversal in AWS aws-parallelcluster, rated medium (5.9 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Relative path segments in input let a caller reach files outside the intended folder.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade AWS aws-parallelcluster to 3.16.0 or later.
- Until it is patched, review who holds accounts that can reach it.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- File storage the service can read or write. The flaw sits between the application and the file system it can reach.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.
Questions to answer about your own systems
- Where does AWS aws-parallelcluster run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.