CVE-2026-73262

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Prowler is a cloud security platform. Prior to 5.37.0, Prowler's HTML output formatter in prowler/lib/outputs/html/html.py inserted finding.resource_tags, assembled by unroll_dict and parse_html_string, into generated reports without HTML escaping, allowing a cloud principal who can modify a scanned resource tag to store HTML or JavaScript that executes when another user opens the report. This issue is fixed in version 5.37.0.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
The EG Score, 5.4 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 12, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 12, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Prowler 5.37.0

Patch available: prowler-cloud/prowler 5.37.0

https://github.com/prowler-cloud/prowler/releases/tag/5.37.0
GitHub commit

commit 6db407ed3c17 (prowler-cloud/prowler)

Fix landed in prowler-cloud/prowler commit 6db407ed3c17 — awaiting tagged release

https://github.com/prowler-cloud/prowler/commit/6db407ed3c17d4c73a8f619fdb30580c8465027f
GitHub pull request

fix(html): escape provider data in reports

Fix merged in prowler-cloud/prowler PR #12221 on 2026-07-30 — awaiting tagged release

https://github.com/prowler-cloud/prowler/pull/12221
GitHub advisoryMentions a patch (unverified)

Stored XSS in HTML reports through unescaped cloud resource tags · Advisory · prowler-cloud/prowler · GitHub

https://github.com/prowler-cloud/prowler/security/advisories/GHSA-c2jg-2778-ggm4

Vendor Advisories for CVE-2026-73262(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
prowler3.1.0 ... 5.9.2 (185 versions)
  • every version up to 5.37.0: fixed in 5.37.0
—
prowler-cloud0.0.0rc1 ... 5.9.2 (202 versions)
  • every version up to 5.37.0: fixed in 5.37.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 99 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 3 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-12 15:41 UTCEG score recompute
  4. 2026-10-11 19:26 UTCEG score recompute
  5. 2026-10-11 16:42 UTCEG score recompute
  6. 2026-10-11 14:02 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-06 17:30 UTCEG score recompute
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-03 20:14 UTCEG score recompute
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-02 08:22 UTCEG score recompute
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-09-30 21:58 UTCEG score recompute
  21. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-09-28 10:59 UTCEG score recompute
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-09-27 09:57 UTCEG score recompute
Show 71 more
  1. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-09-25 03:43 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-09-23 13:33 UTCEG score recompute
  5. 2026-09-22 12:30 UTCEG score recompute
  6. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-09-21 11:19 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-09-20 10:16 UTCEG score recompute
  10. 2026-09-19 08:11 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-09-18 07:09 UTCEG score recompute
  13. 2026-09-17 06:07 UTCEG score recompute
  14. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-09-16 05:04 UTCEG score recompute
  17. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-14 02:01 UTCEG score recompute
  19. 2026-09-13 00:59 UTCEG score recompute
  20. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-11 23:57 UTCEG score recompute
  22. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-09-10 22:30 UTCEG score recompute
  24. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-09 08:02 UTCEG score recompute
  26. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-08 07:00 UTCEG score recompute
  28. 2026-09-07 05:55 UTCEG score recompute
  29. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  30. 2026-09-06 04:17 UTCEG score recompute
  31. 2026-09-05 03:14 UTCEG score recompute
  32. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-09-02 23:39 UTCEG score recompute
  34. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-01 13:14 UTCEG score recompute
  37. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-08-31 11:45 UTCEG score recompute
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-08-30 09:40 UTCEG score recompute
  41. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-08-29 08:38 UTCEG score recompute
  43. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-08-27 13:57 UTCEG score recompute
  46. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-26 12:54 UTCEG score recompute
  48. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  49. 2026-08-25 11:52 UTCEG score recompute
  50. 2026-08-24 10:50 UTCEG score recompute
  51. 2026-08-23 09:48 UTCEG score recompute
  52. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  53. 2026-08-22 08:46 UTCEG score recompute
  54. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  55. 2026-08-21 07:44 UTCEG score recompute
  56. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  57. 2026-08-20 06:42 UTCEG score recompute
  58. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  59. 2026-08-19 05:40 UTCEG score recompute
  60. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  61. 2026-08-18 04:36 UTCEG score recompute
  62. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  63. 2026-08-17 03:31 UTCEG score recompute
  64. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  65. 2026-08-16 02:28 UTCEG score recompute
  66. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  67. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  68. 2026-08-14 00:24 UTCEG score recompute
  69. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  70. 2026-08-12 23:22 UTCEG score recompute
  71. 2026-08-12 22:21 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:prowler-cloud

Frequently asked(5)

What is CVE-2026-73262?
CVE-2026-73262 is a medium-severity vulnerability; its CVE record was published on August 12, 2026. Prowler is a cloud security platform. Prior to 5.37.0, Prowler's HTML output formatter in prowler/lib/outputs/html/html.py inserted finding.resourcetags, assembled by unrolldict and parsehtmlstring, into generated reports without HTML escaping, allowing a cloud principal who can modify a scanned…
When was the CVE record for CVE-2026-73262 published?
The CVE record for CVE-2026-73262 was published on August 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-73262 actively exploited?
CVE-2026-73262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73262?
CVE-2026-73262 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73262?
A fix for CVE-2026-73262 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73262 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73262

Explore →

Is Your Infrastructure Affected by CVE-2026-73262?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs