Metadata forgery via duplicate signature counting
Published Apr 24, 2026 · Updated Apr 24, 2026
Signature verification in AWS tough before 0.22.0 and tuftool before 0.15.0 allows remote authenticated users to accept forged metadata. Delegated-target validation counts repeated valid signatures from the same key toward the threshold instead of requiring distinct keys. Access to one valid delegated-role signing key is required, and exploitation compromises repository metadata integrity without direct confidentiality or availability impact.
Summary
What happened
Signature verification in AWS tough before 0.22.0 and tuftool before 0.15.0 allows remote authenticated users to accept forged metadata. Delegated-target validation counts repeated valid signatures from the same key toward the threshold instead of requiring distinct keys. Access to one valid delegated-role signing key is required, and exploitation compromises repository metadata integrity without direct confidentiality or availability impact.
The record
- CVE
- CVE-2026-6966
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, CAPEC-475, T1553
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo