Vulnerability in Amazon tough (CVE-2026-6966)
Summary
Vulnerability in Amazon tough (CVE-2026-6966). Data can be tampered with by attackers. Mitigation: upgrade to 0.22.0 or later.
Original description
The description as published by the source.
Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users to bypass the TUF signature threshold requirement by duplicating a valid signature, causing the client to accept forged delegated role metadata.
We recommend you upgrade to tough-v0.22.0 / tuftool-v0.15.0.
Source: AWS Security Bulletins NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-6966 has been found in Amazon tough.
Data can be tampered with by attackers.
What to do: upgrade Amazon tough to 0.22.0 or later.
If unsure, ask your IT team or search "Amazon tough CVE-2026-6966" on the vendor's site.
CVE-2026-6966 (Amazon tough) — CWE-347
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.22.0 — apply immediately
Workaround: No workarounds to this issue are known.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in Amazon tough.
Check the vendor advisory for the affected versions of Amazon tough.
Severity: ?. Data can be tampered with by attackers.
Update to 0.22.0.
Workaround: No workarounds to this issue are known.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tough' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tough' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
toughを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No workarounds to this issue are known.パッチが適用されるまでの応急処置として、No workarounds to this issue are known. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade Amazon tough to 0.22.0ステージング環境で 0.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory aws.amazon.com
- advisory github.com
- AWS aws.amazon.com
- package github.com
- patch crates.io
- patch crates.io
- patch github.com
- patch github.com
- web aws.amazon.com