# Attacker can cause Kyverno user to unintentionally consume insecure image

Advisory record · `GHSA-3hfq-cx9j-923w`

- **Identifiers:** `GHSA-3hfq-cx9j-923w` · `BIT-kyverno-2023-47630` · `CVE-2023-47630` · `GO-2023-2340`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-345](https://cwe.mitre.org/data/definitions/345.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 14 Nov 2023
- **Updated:** 7 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Nov 2023, 22:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/kyverno/kyverno` (Go): affected `<1.10.5`; fixed in `1.10.5`

## Machine-written summary

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

> github.com/kyverno/kyverno versions before 1.10.5 can be made to consume an image with a different digest than the one requested. An attacker must first compromise the registry that Kyverno pulls images from, then return a vulnerable or malicious image. Upgrade to version 1.10.5 or later. Users who pull images from trusted registries are not affected.

Written 6 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

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 18th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:53 UTC: First seen by agentprime
- 31 Oct 2026, 14:53 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3hfq-cx9j-923w)

## Sources

- [GitHub Advisory Database: GHSA-3hfq-cx9j-923w](https://github.com/advisories/GHSA-3hfq-cx9j-923w)
- [OSV: GHSA-3hfq-cx9j-923w](https://osv.dev/vulnerability/GHSA-3hfq-cx9j-923w)
- <https://github.com/kyverno/kyverno/security/advisories/GHSA-3hfq-cx9j-923w>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-47630>
- <https://github.com/kyverno/kyverno>
- <https://github.com/kyverno/kyverno/releases/tag/v1.11.0>

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-3hfq-cx9j-923w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3hfq-cx9j-923w/>. Everything for agents: <https://agentprime.io/llms.txt>.