Kyverno policy-reporter-ui has XSS via Stored Property Values in PropertyCard Component

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-44245: 0.18% estimated exploitation activity in the next 30 days; percentile 7.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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 (e.g., <img src=x onerror=alert(1) padded to exceed 75 chars) 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. No DOMPurify or equivalent HTML sanitization library is present anywhere in the frontend codebase, confirming there is no compensating control between the API response and the sink. This vulnerability was reproduced on the latest…

Published by the source

6 May 2026, 22:11 UTC

Last modified by the source

13 May 2026, 16:43 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q98m-7w8c-w388

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44245

Advisory: Kyverno policy-reporter-ui has XSS via Stored Property Values in PropertyCard Component
IDs: CVE-2026-44245, GHSA-q98m-7w8c-w388
Record: https://patchnext.com/advisories/cve-2026-44245 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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/policy-reporter-ui 2.5.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kyverno/policy-reporter-ui: affected <= 2.5.1; fixed in 2.5.2

## Suggested inspection (read-only)
- Go github.com/kyverno/policy-reporter-ui: 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/policy-reporter-ui.
- 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-q98m-7w8c-w388 (GitHub-reviewed advisory GHSA-q98m-7w8c-w388 lists affected ranges: Go github.com/kyverno/policy-reporter-ui >=0 <=2.5.1)

Commands are suggestions: review each one before running it.