{"answers":{"affected":"3 open source packages ship an affected version, including github.com/in-toto/go-witness.","exploited":"There is no known exploitation of CVE-2025-62375 in the wild and no public exploit code.","fix":"Upgrade github.com/in-toto/go-witness to 0.9.1 or later.","what":"CVE-2025-62375 is a medium-severity vulnerability in in-toto go-witness, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62375 and fix it if it is affected.\n\nWhat it is: CVE-2025-62375 is a medium-severity vulnerability in in-toto go-witness, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-62375 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/in-toto/go-witness (Go): affected all versions; fixed in 0.9.1\n- github.com/in-toto/go-witness (Go): affected all versions; fixed in 0.9.1\n- github.com/in-toto/go-witness (Go): affected all versions; fixed in 0.9.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62375/ (Markdown: https://insights.sbomify.com/CVE-2025-62375/index.md)","id":"CVE-2025-62375","markdown":"https://insights.sbomify.com/CVE-2025-62375/index.md","name":"CVE-2025-62375","record":{"aliases":["CLEANSTART-2026-AQ99839","CLEANSTART-2026-EU40217","GHSA-72c7-4g63-hpw5","GO-2025-4028"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go attestation library","requires_auth":"none","summary":"Attackers can bypass AWS EC2 identity verification in go-witness by supplying forged documents, leading to incorrect trust decisions in attestation workflows.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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 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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"go-witness Improper Verification of AWS EC2 Identity Documents","id":"CVE-2025-62375","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"pwn.college DOJO vulnerable to improper authentication in workspace endpoint allowing unauthorized Windows VM access","id":"CVE-2025-62376"},"packages":[{"ecosystem":"Go","fixed":["0.9.1"],"introduced":["0"],"last_affected":[],"package":"github.com/in-toto/go-witness","purl":null,"source":"GHSA-72c7-4g63-hpw5"},{"ecosystem":"Go","fixed":["0.9.1"],"introduced":["0"],"last_affected":[],"package":"github.com/in-toto/go-witness","purl":"pkg:golang/github.com/in-toto/go-witness","source":"GHSA-72c7-4g63-hpw5"},{"ecosystem":"Go","fixed":["0.9.1"],"introduced":["0"],"last_affected":[],"package":"github.com/in-toto/go-witness","purl":"pkg:golang/github.com/in-toto/go-witness","source":"GO-2025-4028"}],"prev":{"headline":"Parse Javascript SDK vulnerable to prototype pollution in `Parse.Object` and internal APIs","id":"CVE-2025-62374"},"products":["go-witness"],"published":"2025-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["in-toto"]},"summary":"Attackers can bypass AWS EC2 identity verification in go-witness by supplying forged documents, leading to incorrect trust decisions in attestation workflows.","url":"https://insights.sbomify.com/CVE-2025-62375/"}