Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73262 medium CVSS 5.4

Cross-Site Scripting (XSS) in prowler (CVE-2026-73262)

Summary

Cross-site scripting in prowler (CVE-2026-73262). Risk of unauthorized operations or information disclosure. Exploitable via finding.resource_tags. Mitigation: upgrade to 5.37.0 or later.

Original description

The description as published by the source.

Summary

Prowler's HTML output formatter inserts finding.resource_tags into the generated report without HTML escaping. A cloud principal who can create or edit a resource tag in an account that is later scanned can store HTML or JavaScript in that tag. When another user opens the generated Prowler HTML report, the payload executes in the report page.

Impact

This is stored cross-site scripting in a security report artifact. The attacker needs permission to influence tags on a scanned cloud resource, and the victim must open the generated HTML report. In that context, JavaScript can read and modify the report DOM, alter displayed findings, and interact with any same-origin local or hosted report content available to the browser. This can undermine trust in generated security findings and can expose data contained in the report page.

Gate checks

The repository has 13,875 GitHub stars, which is above the 10,000 star floor. SECURITY.md is present and does not reject GitHub private reporting. The dedicated GitHub private vulnerability reporting endpoint for prowler-cloud/prowler returned true.

Affected versions

The vulnerable sink is present in current master at commit 329dfdf8e6cb8bc0424fb54b6595408e20969782 and in the latest GitHub release tag 5.28.0. The package metadata identifies the Python package as prowler.

Technical details

The HTML formatter builds each finding row with an f-string in prowler/lib/outputs/html/html.py. Neighboring…

Source: NIST National Vulnerability Database 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-73262 has been found in prowler.
Attackers can target a specific entry point like finding.resource_tags over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade prowler to 5.37.0 or later.
If unsure, ask your IT team or search "prowler CVE-2026-73262" on the vendor's site.

CVE-2026-73262 (prowler) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: finding.resource_tags / SECURITY.md / true / master
Patched: 5.37.0 — apply immediately
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.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in prowler. Attackers reach the vulnerable code path via finding.resource_tags.

📍 Affected scope

Check the vendor advisory for the affected versions of prowler. Attack surface: finding.resource_tags / SECURITY.md / true / master.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.37.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'prowler' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'prowler' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で prowler を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade prowler to 5.37.0

    ステージング環境で 5.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip prowler
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.37.0"}]}]
pip prowler-cloud
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.37.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details