Cross-Site Scripting (XSS) in Pen Drive report generator (CVE-2026-13083)
Summary
Cross-site scripting in Pen Drive report generator (CVE-2026-13083). Confidential information can be exposed externally.
Original description
The description as published by the source.
A flaw was found in the Pen Drive report generator. Cluster-sourced data is rendered into HTML reports without proper escaping or sanitization. An attacker with cluster administrator privileges can inject a stored cross-site scripting (XSS) payload into cluster objects (such as ClusterVersion spec.channel) that executes in the browser of any user who opens the generated HTML report.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-13083 has been found in Pen Drive report generator.
Confidential information can be exposed externally. CVSS score: 6.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Pen Drive report generator CVE-2026-13083" on the vendor's site.
CVE-2026-13083 (Pen Drive report generator) — CWE-79 / CVSS v3 6.9
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Pen Drive report generator.
Check the vendor advisory for the affected versions of Pen Drive report generator.
Severity: Medium (CVSS 6.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Pen Drive report generator を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch secalert@redhat.com
- patch secalert@redhat.com
- web nvd.nist.gov
- web github.com