CVE-2026-44245 Kyverno: [policy-reporter-ui] XSS via Stored Property Values in PropertyCard Component
Attackers can inject malicious HTML into the Kyverno policy reporter UI via stored policy report properties, potentially executing scripts in the user's browser.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-44245?
CVE-2026-44245 is a medium-severity cross-site scripting vulnerability in kyverno, published on 12 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to 2.5.2, Vue 3's v-html directive is the framework-documented mechanism for injecting raw HTML, and it intentionally disables the auto-escaping that {{ }} interpolation provides. The PropertyCard.vue component uses v-html for the else branch of the URL check, meaning any non-URL string value flows directly into the DOM as HTML. The isURL() guard only filters values that parse as http: or https: URLs, so any HTML payload not starting with those schemes bypasses it entirely. The data originates from Kubernetes PolicyReport .results[].properties fields, which are arbitrary string maps populated by policy engines and potentially by any principal with write access to PolicyReport objects in the cluster. This vulnerability is fixed in 2.5.2.
Weakness: CWE-79
Which versions are affected by CVE-2026-44245?
4 open source packages ship an affected version, including github.com/kyverno/policy-reporter-ui and kyverno. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/kyverno/policy-reporter-ui Go | All versions | 2.5.2 |
github.com/kyverno/policy-reporter-ui Go | All versions | 2.5.2 |
github.com/kyverno/policy-reporter-ui Go | All versions | 2.5.2+incompatible |
kyverno Bitnami | All versions | 2.5.2 |
Products include Kyverno Policy-Reporter-Ui.
How do I fix CVE-2026-44245?
Upgrade github.com/kyverno/policy-reporter-ui to a fixed version for your release line: 2.5.2 or 2.5.2+incompatible.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-44245 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44245 exists.
Sources
Also known as BIT-kyverno-2026-44245, GHSA-q98m-7w8c-w388, GO-2026-5577.