CVE-2026-75531

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Pandora contains a stored cross-site scripting (XSS) vulnerability in the rendering of URL observables. A URL extracted from or associated with an analyzed file was inserted directly into the inline JavaScript onclick handler used by the Submit to Lookyloo action.

Although the value was subject to HTML escaping by the template engine, it was embedded inside a JavaScript string within an HTML attribute. An attacker-controlled URL containing specially crafted characters could therefore break out of the JavaScript string and inject arbitrary JavaScript code.

The malicious script would execute in the context of the Pandora web application when a victim interacts with the affected Submit to Lookyloo control. Successful exploitation could allow an attacker to access information available to the victim's browser or perform actions using the victim's authenticated Pandora session.

The patch removes the observable value from the inline JavaScript handler. The URL is instead stored in an HTML data-url attribute and retrieved through the DOM dataset API when needed. Additional uses of innerHTML were also replaced with textContent as defensive hardening.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 17, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit 77a84a039e20 (pandora-analysis/pandora)

Patch available: pandora-analysis/pandora v1.12.6 (contains commit 77a84a039e20)

https://github.com/pandora-analysis/pandora/commit/77a84a039e2079dba7ea0342816c9813099d75d0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-27 19:25 UTCEG score recompute
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 17:14 UTCEG score recompute
  5. 2026-08-26 14:47 UTCEPSS rescore
  6. 2026-08-25 17:06 UTCEG score recompute
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-24 17:07 UTCEG score recompute
  9. 2026-08-24 14:18 UTCEPSS rescore
  10. 2026-08-23 04:39 UTCEG score recompute
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 04:42 UTCEG score recompute
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 04:46 UTCEG score recompute
  15. 2026-08-20 22:56 UTCEPSS rescore
  16. 2026-08-20 04:42 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 16:44 UTCEG score recompute
  19. 2026-08-18 15:33 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-17 21:30 UTCEG score recompute
  23. 2026-08-17 21:05 UTCEG score recompute
  24. 2026-08-17 21:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75531?
CVE-2026-75531 is a high vulnerability published on August 17, 2026. Pandora contains a stored cross-site scripting (XSS) vulnerability in the rendering of URL observables. A URL extracted from or associated with an analyzed file was inserted directly into the inline JavaScript onclick handler used by the Submit to Lookyloo action. Although the value was subject to…
When was CVE-2026-75531 disclosed?
CVE-2026-75531 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75531 actively exploited?
CVE-2026-75531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.1% of all scored CVEs.
What is the CVSS score of CVE-2026-75531?
CVE-2026-75531 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-75531?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75531, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75531

Explore →

Is Your Infrastructure Affected by CVE-2026-75531?

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