CVE-2026-6968: AWS tough · Path Traversal
Affects AWS toughSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.22.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.22.0, 0.15.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade tough and awslabs/tough to 0.22.0; tuftool and awslabs/tuftool to 0.15.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWStough | Affected
| Fixed in
|
| AWStuftool | Affected
| Fixed in
|
crates.ioawslabs/toughpkg:cargo/awslabs/toughOther threats | Affected
| Fixed in
|
crates.ioawslabs/tuftoolpkg:cargo/awslabs/tuftoolOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
AWS recommends upgrading to tough version 0.22.0 or tuftool version 0.15.0, which contain fixes for this path traversal vulnerability. Since this is a cloud service component, AWS manages remediation for the cloud-hosted service. Users should verify they are using the patched versions and consult the AWS security bulletin at https://aws.amazon.com/security/security-bulletins/2026-019-aws/ for the latest guidance.
Description
Incomplete path traversal fixes in awslabs/tough before tough-v0.22.0 allow remote authenticated users with delegated signing authority to write files outside intended output directories via absolute target names in copy_target/link_target, symlinked parent directories in save_target, or symlinked metadata filenames in SignedRole::write, because write paths trust the joined destination path without post-resolution containment verification. We recommend you upgrade to tough-v0.22.0 / tuftool-v0.15.0.
References
- aws.amazon.com/security/security-bulletins/2026-019-aws/ (opens in a new tab)
- github.com/awslabs/tough/releases/tag/tough-v0.22.0 (opens in a new tab)
- github.com/awslabs/tough/releases/tag/tuftool-v0.15.0 (opens in a new tab)
- crates.io/crates/tough/0.22.0 (opens in a new tab)
- crates.io/crates/tuftool/0.15.0 (opens in a new tab)
- github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg (opens in a new tab)