1sealsemantic last-mile verification

Research / Finding

Signature Threshold Bypass in awslabs/tough Delegated Roles

F-AWS-TOUGH-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

5.3medium
CVE-2026-6966CVEawslabs/tough

Signature Threshold Bypass in awslabs/tough Delegated Roles

Fixed in: tough 0.22.0, tuftool 0.15.0

patched
details
Finding IDs
F-AWS-TOUGH-001
CVE
CVE-2026-6966
GHSA
GHSA-8m7c-8m39-rv4x
Status
patched
Fixed in
tough 0.22.0, tuftool 0.15.0
Recorded credit
reporter: @1seal; acknowledgement: Oleh Konko of 1seal
Note
GHSA-8m7c-8m39-rv4x · signature threshold bypass in delegated roles
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
CVE registry state
PUBLISHED
CVE state checked
Upstream title
Signature Threshold Bypass in awslabs/tough Delegated Roles
Upstream publication
Upstream updated
Metadata fetched
Upstream @1seal credit
@1seal: reporter (accepted)

F-AWS-TOUGH-001: Verification failures. Metadata signature thresholds are not correctly enforced. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-AWS-TOUGH-001

Security area (1seal assessment): Authorization. Metadata signature thresholds are not correctly enforced. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.