GHSA-2q59-h24c-w6fg is a high-severity (CVSS 7.5) CWE-73 vulnerability in voila. A fix is available for voila — see the affected versions and patch details below.
Voilà Local file inclusion
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2q59-h24c-w6fg.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2q59-h24c-w6fg plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
voila🐍voila🐍voila🐍voilaReal-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
Impact
Any deployment of voilà dashboard allow local file inclusion, that is to say any file on a filesystem that is readable by the user that runs the voilà dashboard server can be downloaded by someone with network access to the server.
Whether this still requires authentication depends on how voilà is deployed.
Patches
This is patched in 0.2.17+, 0.3.8+, 0.4.4+, 0.5.6+
Workarounds
None.
References
CWE-73: External Control of File Name or Path
Original report
I have found a local file inclusion vulnerability in one of your subprojects, voila (https://github.com/voila-dashboards/voila).
The vulnerability exists in the "/static" Route, and can be exploited by simply making a request such as this:
$ curl localhost:8866/static/etc/passwd
...or by using a webbrowser to download the file.
I dug into the source code, and I think the offending line is here: https://github.com/voila-dashboards/voila/blob/8419cc7d79c0bb1dabfbd9ec49cb957740609d4d/voila/app.py#L664
"static_path" gets set to "/", irrespective of the actual "--static" cli option. Because of that, the tornado.web.StaticFileHandler gets initialized with path="/". Then, tornado.web.StaticFileHandler.get calls tornado.web.StaticFileHandler.get_absolute_path with root="/" and path="[USER SUPPLIED PATH]", which leads to local file inclusion. An attacker can request any file on the system they want (that the user running voila has access to).
I suspect this was an oversight during development. Setting static_path=self.static_root (the aforementioned correct cli option) in line 664 provides the intended behavior and restricts the file access to the static directory.
From what I can tell, this line has been in the repository since September 2018. This is the commit that added it: https://github.com/voila-dashboards/voila/commit/28faacc9b03b160fd8fa920ad045f4ec0667ab67
I have found multiple voila instances online that are impacted, such as:
- ... [redacted]
- ... [redacted]
- ... [redacted]
...but many more probably exist. They're easy to identify by [redacted] Therefore the Issue should be fixed as soon as possible, and a security advisory should be released to inform the impacted users.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | voila | ≥ 0.0.2&&< 0.2.17 | 0.2.17pip install --upgrade 'voila==0.2.17' |
| 🐍PyPI | voila | ≥ 0.3.0a0&&< 0.3.8 | 0.3.8pip install --upgrade 'voila==0.3.8' |
| 🐍PyPI | voila | ≥ 0.4.0a0&&< 0.4.4 | 0.4.4pip install --upgrade 'voila==0.4.4' |
| 🐍PyPI | voila | ≥ 0.5.0a0&&< 0.5.6 | 0.5.6pip install --upgrade 'voila==0.5.6' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for voila, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update voila to 0.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2q59-h24c-w6fg 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2q59-h24c-w6fg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2q59-h24c-w6fg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2q59-h24c-w6fg in your dependencies?
O3 Security finds GHSA-2q59-h24c-w6fg across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.