# CVE-2026-124033: Relative path traversal in the log export commands in AWS ParallelCluster CLI


- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-h79v-mp93-644r

## What is CVE-2026-124033?

CVE-2026-124033 is a medium-severity vulnerability in aws-parallelcluster, published on 9 Nov 2026. 

### Official 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.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-124033?


## How do I fix CVE-2026-124033?

No fix has been published for CVE-2026-124033 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124033 being exploited?

There is no known exploitation of CVE-2026-124033 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124033 and fix it if it is affected.

What it is: CVE-2026-124033 is a medium-severity vulnerability in aws-parallelcluster, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124033 in the wild and no public exploit code.

Affected product: aws-parallelcluster. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124033/ (Markdown: https://insights.sbomify.com/CVE-2026-124033/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124033
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124033
- OSV: https://osv.dev/vulnerability/CVE-2026-124033

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124033/
Summaries are generated and may contain mistakes; the official description above is the record.