How severe is GHSA-939m-4xpw-v34v?

GHSA-939m-4xpw-v34v has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-939m-4xpw-v34v?

GHSA-939m-4xpw-v34v affects the following packages: blazar-dashboard (PyPI), blazar-dashboard (PyPI), blazar-dashboard (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-939m-4xpw-v34v?

Update blazar-dashboard to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-939m-4xpw-v34v is resolved across your whole dependency graph.

How do I detect GHSA-939m-4xpw-v34v in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for blazar-dashboard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-939m-4xpw-v34v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-939m-4xpw-v34v actively exploited in the wild?

No public exploit code has been indexed for GHSA-939m-4xpw-v34v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-939m-4xpw-v34v?

GHSA-939m-4xpw-v34v has an EPSS (Exploit Prediction Scoring System) score of 3.3%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-939m-4xpw-v34v published, and has it been updated?

GHSA-939m-4xpw-v34v was published on October 27, 2020 and was last updated on September 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

Arbitrary Code Execution in blazar-dashboardGHSA-939m-4xpw-v34v

CRITICAL

GHSA-939m-4xpw-v34v is a critical-severity (CVSS 9.9) remote code execution vulnerability in blazar-dashboard. A fix is available for blazar-dashboard — see the affected versions and patch details below.

Also known asCVE-2020-26943PYSEC-2020-225

Published

Oct 27, 2020

Updated

Sep 6, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-939m-4xpw-v34v by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

🐍blazar-dashboard🐍blazar-dashboard🐍blazar-dashboard

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in OpenStack blazar-dashboard before 1.3.1, 2.0.0, and 3.0.0. A user allowed to access the Blazar dashboard in Horizon may trigger code execution on the Horizon host as the user the Horizon service runs under (because the Python eval function is used). This may result in Horizon host unauthorized access and further compromise of the Horizon service. All setups using the Horizon dashboard with the blazar-dashboard plugin are affected.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`blazar-dashboard`	all versions	1.3.1`pip install --upgrade 'blazar-dashboard==1.3.1'`
🐍PyPI	`blazar-dashboard`	≥ 2.0.0&&< 2.0.1	2.0.1`pip install --upgrade 'blazar-dashboard==2.0.1'`
🐍PyPI	`blazar-dashboard`	≥ 3.0.0&&< 3.0.1	3.0.1`pip install --upgrade 'blazar-dashboard==3.0.1'`

Affected Products

1 product · 3 configurations

Application

blazar-dashboardopenstack

< 1.3.1

2 versions

2.0.03.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for blazar-dashboard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update blazar-dashboard to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-939m-4xpw-v34v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-939m-4xpw-v34v in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works