GHSA-8m7c-8m39-rv4x: compound delegation chain decomposed across CVE-2026-6966 and CVE-2026-6967

compound delegation chain decomposed across CVE-2026-6966 and CVE-2026-6967

F-AWS-TOUGH-DELEGATION-CHAIN-001

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

Recorded evidence

—score not recorded

awslabs/toughReported fixawslabs/tough

compound delegation chain decomposed across CVE-2026-6966 and CVE-2026-6967

fixed publicly

details

Finding IDs: F-AWS-TOUGH-DELEGATION-CHAIN-001
GHSA: GHSA-8m7c-8m39-rv4x
Status: fixed publicly
Reported via: security contact
Note: upstream fixed and publicly released on 2026-04-24 in tough 0.22.0 / tuftool 0.15.0. the reported compound chain is publicly decomposed across GHSA-8m7c-8m39-rv4x / CVE-2026-6966 and GHSA-4v58-8p28-2rq3 / CVE-2026-6967 rather than published as a single bundled advisory.

F-AWS-TOUGH-DELEGATION-CHAIN-001: Verification failures. The compound report concerns metadata/delegation trust checks; related receipts do not create an independent defect count. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-AWS-TOUGH-DELEGATION-CHAIN-001

Security area (1seal assessment): Authorization. The compound report concerns metadata/delegation trust checks; related receipts do not create an independent defect count. 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.