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

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

- **Identifiers:** `GHSA-xhg5-42rf-296r` · `CVE-2023-33959` · `GO-2023-1832`
- **State:** Confirmed
- **Severity:** CVSS 8.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-347](https://cwe.mitre.org/data/definitions/347.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 6 Jun 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/notaryproject/notation-go` (Go): affected `<1.0.0-rc.6`; fixed in `1.0.0-rc.6`

## 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

- 8.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`, from 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

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xhg5-42rf-296r)

## Sources

- [GitHub Advisory Database: GHSA-xhg5-42rf-296r](https://github.com/advisories/GHSA-xhg5-42rf-296r)
- [OSV: GHSA-xhg5-42rf-296r](https://osv.dev/vulnerability/GHSA-xhg5-42rf-296r)
- <https://github.com/notaryproject/notation-go/security/advisories/GHSA-xhg5-42rf-296r>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-33959>
- <https://github.com/notaryproject/notation-go/commit/39c8ed050a65cca3f3f308534acb612096735a64>
- <https://github.com/notaryproject/notation-go/commit/eba60f5aed9c9e05dee55324423c95fe34700b4c>
- <https://github.com/notaryproject/notation-go>
- <https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.6>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xhg5-42rf-296r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xhg5-42rf-296r/>. Everything for agents: <https://agentprime.io/llms.txt>.
