# 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.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** Yes
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** BIT-kyverno-2026-44245, GHSA-q98m-7w8c-w388, GO-2026-5577

## 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 (Improper Neutralization of Input During Web Page Generation)

## 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 | Ecosystem | 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: 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.

## Is CVE-2026-44245 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44245 exists.

## Fix prompt for AI coding agents

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

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44245 exists.

Affected packages and fixed versions:
- github.com/kyverno/policy-reporter-ui (Go): affected all versions; fixed in 2.5.2
- github.com/kyverno/policy-reporter-ui (Go): affected all versions; fixed in 2.5.2
- github.com/kyverno/policy-reporter-ui (Go): affected all versions; fixed in 2.5.2+incompatible
- kyverno (Bitnami): affected all versions; fixed in 2.5.2

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

## Sources

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

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