Advisory record · GHSA-xhg5-42rf-296r

notation-go's verification bypass can cause users to verify the wrong artifact

CVSS 8.4 HighEPSS 0.0035 · 29th percentile

Published by the GitHub Advisory Database at 6 Jun 2023, 16:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/notaryproject/notation-goGo<1.0.0-rc.61.0.0-rc.6
Identifiers
GHSA-xhg5-42rf-296r · CVE-2023-33959 · GO-2023-1832
Weakness (CWE)
CWE-347
Published
6 Jun 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The notation-go Go library is vulnerable in versions before 1.0.0-rc.6. An attacker who controls or compromises a registry can cause a user to verify the wrong artifact. Upgrade to notation-go v1.0.0-rc.6 or later. The source suggests using only secure and trusted container registries as a workaround.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0035, the 29th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.