# CVE-2026-29773: kubewarden-controller cross-namespace data exfiltration via deprecated host callback binding

> Attackers with specific policy creation permissions can read Ingress, Namespace, and Service resources across namespaces via deprecated APIs.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-6r7f-3fwq-hq74, GO-2026-4652

## What is CVE-2026-29773?

CVE-2026-29773 is a medium-severity missing authorization vulnerability in kubewarden-controller, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kubewarden is a policy engine for Kubernetes. Kubewarden cluster operators can grant permissions to users to deploy namespaced AdmissionPolicies and AdmissionPolicyGroups in their Namespaces. One of Kubewarden promises is that configured users can deploy namespaced policies in a safe manner, without privilege escalation. An attacker with privileged "AdmissionPolicy" create permissions (which isn't the default) could make use of 3 deprecated host-callback APIs: kubernetes/ingresses, kubernetes/namespaces, kubernetes/services. The attacker can craft a policy that exercises these deprecated API calls and would allow them read access to Ingresses, Namespaces, and Services resources respectively. 
This attack is read-only, there is no write capability and no access to Secrets, ConfigMaps, or other resource types beyond these three.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-29773?

3 open source packages ship an affected version, including github.com/kubewarden/kubewarden-controller. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubewarden/kubewarden-controller` | Go | All versions | 1.33.0 |
| `github.com/kubewarden/kubewarden-controller` | Go | All versions | 1.33.0 |
| `github.com/kubewarden/kubewarden-controller` | Go | All versions | 1.33.0 |

Products: Linuxfoundation Kubewarden.

## How do I fix CVE-2026-29773?

Upgrade github.com/kubewarden/kubewarden-controller to 1.33.0 or later.

## Is CVE-2026-29773 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29773 and fix it if it is affected.

What it is: CVE-2026-29773 is a medium-severity missing authorization vulnerability in kubewarden-controller, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29773 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kubewarden/kubewarden-controller (Go): affected all versions; fixed in 1.33.0
- github.com/kubewarden/kubewarden-controller (Go): affected all versions; fixed in 1.33.0
- github.com/kubewarden/kubewarden-controller (Go): affected all versions; fixed in 1.33.0

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-2026-29773/ (Markdown: https://insights.sbomify.com/CVE-2026-29773/index.md)
```

## Sources

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

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