go-witness and witness are Go modules for generating attestations. In go-witness versions 0.8.6 and earlier and witness versions 0.9.2 and earlier the AWS attestor improperly verifies AWS EC2 instance identity documents. Verification can in…
Exact source revision recorded 9 Nov 2026 04:05:43 UTC. It does not establish the source's current position. Latest evidence.
euvd · EUVD-2025-34679
Publishedgo-witness and witness are Go modules for generating attestations. In go-witness versions 0.8.6 and earlier and witness versions 0.9.2 and earlier the AWS attestor improperly verifies AWS EC2 instance identity documents. Verification can incorrectly succeed when a signature is not present or is empty, and when RSA signature verification fails. The attestor also embeds a single legacy global AWS public certificate and does not account for newer region specific certificates issued in 2024, making detection of forged documents difficult without additional trusted region data. An attacker able to supply or intercept instance identity document data (such as through Instance Metadata Service impersonation) can cause a forged identity document to be accepted, leading to incorrect trust decisions based on the attestation. This is fixed in go-witness 0.9.1 and witness 0.10.1. As a workaround, manually verify the included identity document, signature, and public key with standard tools (for example openssl) following AWS’s verification guidance, or disable use of the AWS attestor until upgraded.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 15, 2025, 7:23:24 PM
dateUpdated: Oct 15, 2025, 7:44:29 PM
1 related source bulletins · separate from aliases
openSUSE-SU-2025:15710-1: govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media
CVE-2016-11063 · CVE-2016-11066 · CVE-2016-11067 · CVE-2016-11068 · CVE-2016-11069 · CVE-2016-11070 · CVE-2016-11071 · CVE-2016-11072 · CVE-2016-11073 · CVE-2016-11074 · CVE-2016-11075 · CVE-2016-11076 · CVE-2016-11077 · CVE-2016-11078 · CVE-2016-11079 · CVE-2016-11080 · CVE-2016-11081 · CVE-2016-11082 · CVE-2016-11083 · CVE-2016-11084 · CVE-2017-18872 · CVE-2023-32199 · CVE-2024-58269 · CVE-2025-10545 · CVE-2025-10678 · CVE-2025-10954 · CVE-2025-11374 · CVE-2025-11375 · CVE-2025-11579 · CVE-2025-11621 · CVE-2025-12044 · CVE-2025-26625 · CVE-2025-27093 · CVE-2025-41410 · CVE-2025-41443 · CVE-2025-54286 · CVE-2025-54287 · CVE-2025-54288 · CVE-2025-54289 · CVE-2025-54290 · CVE-2025-54291 · CVE-2025-54293 · CVE-2025-54469 · CVE-2025-54470 · CVE-2025-54471 · CVE-2025-54499 · CVE-2025-58073 · CVE-2025-58075 · CVE-2025-58356 · CVE-2025-59043 · CVE-2025-59048 · CVE-2025-59530 · CVE-2025-59836 · CVE-2025-59937 · CVE-2025-61141 · CVE-2025-61524 · CVE-2025-61581 · CVE-2025-61688 · CVE-2025-62156 · CVE-2025-62157 · CVE-2025-62375 · CVE-2025-62506 · CVE-2025-62513 · CVE-2025-62705 · CVE-2025-62714 · CVE-2025-62725 · CVE-2025-62820 · CVE-2025-64101 · CVE-2025-64102 · CVE-2025-64103
- Source published
- Oct 15, 2025, 7:23:24 PM (timezone not stated)
- Source modified
- Oct 15, 2025, 7:44:29 PM (timezone not stated)
- Observed here
- 9 Nov 2026 04:05:43 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 4.0 · 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N