Skip to main content
VulnerabilityPublished Updated

CVE-2026-6967: AWS tough · Insufficient Verification of Data Authenticity

Affects AWS toughSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.22.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 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 30 Oct 2026.

What to do

Upgrade AWS tough to 0.22.0.

Affected software

ProductAffectedFixed in
AWStoughAffected
  • >=0.9.0 <=0.21
Fixed in–
AWStuftoolAffected
  • <=0.14
Fixed in–
crates.iotoughpkg:cargo/toughOther threatsAffected
  • <0.22.0
Fixed in
  • 0.22.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available. AWS recommends upgrading to tough version 0.22.0 or tuftool version 0.15.0 to address this vulnerability. Since this is a cloud service, AWS manages remediation server-side; users should verify they are using updated versions or check the AWS security bulletin at https://aws.amazon.com/security/security-bulletins/2026-019-aws/ for current guidance.

Description

Missing expiration, hash, and length enforcement in delegated metadata validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users with delegated signing authority to bypass TUF specification integrity checks for delegated targets metadata and poison the local metadata cache, because load_delegations does not apply the same validation checks as the top-level targets metadata path. We recommend you upgrade to tough-v0.22.0 / tuftool-v0.15.0.

References

Community reviews

Loading reviews…