Quick answers
- Is CVE-2026-124033 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124033 being exploited in the wild.
- How severe is CVE-2026-124033?
- High severity, with a CVSS score of 6.4, published 9 November 2026.
- Which products and versions are affected?
- AWS ParallelCluster CLI 3.0.0 to 3.15.x.
- Is there a fix for CVE-2026-124033?
- Yes: fixed in 3.16.0. Until then: Restrict write access to the Amazon S3 bucket used for log export to only trusted users who need to perform log exports. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124033 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-124033?
- Check whether you run Amazon AWS or AWS ParallelCluster CLI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.16.0
Restrict write access to the Amazon S3 bucket used for log export to only trusted users who need to perform log exports.
Technical details
A relative path traversal vulnerability exists in the export-cluster-logs and export-image-logs commands where an attacker with authenticated write access to the S3 bucket can craft a malicious S3 object key using path traversal sequences (e.g., "../") to write files outside the intended export directory. The created files would be written with names and content controlled by the attacker and inherit the privileges of the user running the CLI command, potentially leading to arbitrary file write and local privilege escalation.
Affected products
- AWS ParallelCluster CLI 3.0.0 to 3.15.x
Timeline
- 2026-11-09: disclosed