# CVE-2022-47633: kyverno verifyImages rule bypass possible with malicious proxy/registry

> Attackers can bypass image signature validation to inject unsigned container images into Kubernetes clusters, potentially executing arbitrary code.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** BIT-kyverno-2022-47633, GHSA-m3cq-xcx9-3gvm, GO-2022-1180

## What is CVE-2022-47633?

CVE-2022-47633 is a high-severity vulnerability in n/a, published on 23 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An image signature validation bypass vulnerability in Kyverno 1.8.3 and 1.8.4 allows a malicious image registry (or a man-in-the-middle attacker) to inject unsigned arbitrary container images into a protected Kubernetes cluster. This is fixed in 1.8.5. This has been fixed in 1.8.5 and mitigations are available for impacted releases.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-47633?

4 open source packages ship an affected version, including github.com/kyverno/kyverno and kyverno. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kyverno/kyverno` | Go | From 1.8.3 | 1.8.5 |
| `github.com/kyverno/kyverno` | Go | From 1.8.3 | 1.8.5 |
| `github.com/kyverno/kyverno` | Go | From 1.8.3 | 1.8.5 |
| `kyverno` | Bitnami | From 1.8.3 to 1.8.3 | None |

Products: Kyverno Kyverno.

## How do I fix CVE-2022-47633?

Upgrade github.com/kyverno/kyverno to 1.8.5 or later.

## Is CVE-2022-47633 being exploited?

There is no known exploitation of CVE-2022-47633 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-22039](https://insights.sbomify.com/CVE-2026-22039/): Kyverno Cross-Namespace Privilege Escalation via Policy apiCall (critical 10.0)
- [CVE-2026-4789](https://insights.sbomify.com/CVE-2026-4789/): CVE-2026-4789 (critical 9.8)
- [CVE-2025-46342](https://insights.sbomify.com/CVE-2025-46342/): Kyverno vulnerable to bypass of policy rules that use namespace selectors in match statements (high 8.6)
- [CVE-2026-41323](https://insights.sbomify.com/CVE-2026-41323/): Kyverno: ServiceAccount token leaked to external servers via apiCall service URL (high 8.1)
- [CVE-2026-40868](https://insights.sbomify.com/CVE-2026-40868/): kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47633 and fix it if it is affected.

What it is: CVE-2022-47633 is a high-severity vulnerability in n/a, published on 23 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47633 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kyverno/kyverno (Go): affected from 1.8.3; fixed in 1.8.5
- github.com/kyverno/kyverno (Go): affected from 1.8.3; fixed in 1.8.5
- github.com/kyverno/kyverno (Go): affected from 1.8.3; fixed in 1.8.5
- kyverno (Bitnami): affected from 1.8.3 up to 1.8.3; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-47633/ (Markdown: https://insights.sbomify.com/CVE-2022-47633/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-47633
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-47633
- OSV: https://osv.dev/vulnerability/CVE-2022-47633

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-47633/
Summaries are generated and may contain mistakes; the official description above is the record.