Skip to main content
VulnerabilityPublished

CVE-2026-124033: aws-parallelcluster · Relative Path Traversal

Affects aws-parallelclusterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium : upgrade to 3.16.0 when convenient.

Data as of 9 Nov 2026, 21:19 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (AMZN)CVSS 3.16.4
CNA (AMZN)CVSS 4.05.9
Patch
Available – fixed in 3.16.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade aws-parallelcluster to 3.16.0.

Affected software

ProductAffectedFixed in
AWSaws-parallelclusterAffected
  • >=3.0.0 <3.16.0
Fixed in
  • 3.16.0

AI-suggested

Users should upgrade AWS ParallelCluster CLI to version 3.16.0 or later to remediate this vulnerability. Since a patch is available and the fixed version is explicitly stated, applying this official fix is the recommended mitigation.

Description

A relative path traversal vulnerability exists in AWS ParallelCluster CLI versions before 3.16.0 in the export-cluster-logs and export-image-logs commands. An authenticated user with write access to the log export S3 bucket can craft object keys to write files outside the intended directory on the machine running the command, potentially leading to arbitrary file creation with the privileges of the user running the command. This issue is fixed in version 3.16.0.

Reports on CVE-2026-124033

References

Community reviews

Loading reviews…