Attacker can cause Kyverno user to unintentionally consume insecure image
CVE-2023-47630GHSA-3hfq-cx9j-923w
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/kyverno/kyverno 1.10.5), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 1.10.5
- Fixed in
- 1.10.5
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3hfq-cx9j-923w lists affected ranges: Go github.com/kyverno/kyverno >=0 <1.10.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
- EPSS
- CVE-2023-47630: 0.26% estimated exploitation activity in the next 30 days; percentile 18.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
An issue was found in Kyverno that allowed an attacker to control the digest of images used by Kyverno users. The issue would require the attacker to compromise the registry that the Kyverno fetch their images from. The attacker could then return a vulnerable image to the the user and leverage that to further escalate their position. As such, the attacker would need to know which images the Kyverno user consumes and know of one of multiple exploitable vulnerabilities in previous digests of the images. Alternatively, if the attacker has compromised the registry, they could craft a malicious image with a different digest with intentionally placed vulnerabilities and deliver the image to the user. An attacker was not be able to control other parameters of the image than the digest by exploiting this vulnerability. Users pulling their images from trusted registries are not impacted by this vulnerability. There is no evidence of this being exploited in the wild. The issue has been patched…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-3hfq-cx9j-923w
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-47630 Advisory: Attacker can cause Kyverno user to unintentionally consume insecure image IDs: CVE-2023-47630, GHSA-3hfq-cx9j-923w Record: https://patchnext.com/advisories/cve-2023-47630 (revision 1, source checked 26 Oct 2026, 15:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/kyverno/kyverno 1.10.5. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/kyverno/kyverno: affected < 1.10.5; fixed in 1.10.5 ## Suggested inspection (read-only) - Go github.com/kyverno/kyverno: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/kyverno/kyverno. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-3hfq-cx9j-923w (GitHub-reviewed advisory GHSA-3hfq-cx9j-923w lists affected ranges: Go github.com/kyverno/kyverno >=0 <1.10.5) Commands are suggestions: review each one before running it.
Loading voting…