GHSA-j3jp-gvr5-7hwq — python-engineio
HIGHGHSA-j3jp-gvr5-7hwq is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in python-engineio. A fix is available for python-engineio — see the affected versions and patch details below.
python-engineio vulnerable to Cross-Site Request Forgery (CSRF)
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-j3jp-gvr5-7hwq 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 379,145 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
python-engineioReal-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
WebSocket cross-origin vulnerability
Impact
This is a Cross-Site Request Forgery (CSRF) vulnerability. It affects Socket.IO and Engine.IO web servers that authenticate clients using cookies.
Patches
python-engineio version 3.9.0 patches this vulnerability by adding server-side Origin header checks.
Workarounds
Do not use cookies for client authentication, or else add a CSRF token to the connection URL.
References
https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF) https://www.christian-schneider.net/CrossSiteWebSocketHijacking.html
For more information
If you have any questions or comments about this advisory:
- Open an issue in python-engineio
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | python-engineio | all versions | 3.9.0pip install --upgrade 'python-engineio==3.9.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for python-engineio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update python-engineio to 3.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3jp-gvr5-7hwq 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-j3jp-gvr5-7hwq can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j3jp-gvr5-7hwq. 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-j3jp-gvr5-7hwq in your dependencies?
O3 Security finds GHSA-j3jp-gvr5-7hwq across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.