Taipy 3.1.1 affected by CVEs on flask-core and pymongoGHSA-pp84-v3mw-gg4w
GHSA-pp84-v3mw-gg4w is a security vulnerability in taipy. A fix is available for taipy — see the affected versions and patch details below.
Real-World Exposure
taipyReal-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
Summary
Indirect CVEs affect Taipy 3.1.1
Details
Taipy 3.1.1 is affected by two existing CVEs: CVE-2024-1681 affects flask-core <4.0.1 and taipy 3.1.1 needs <=4.0.0 CVE-2024-5629 affects pymongo <4.6.3 and taipy 3.1.1 needs <=4.6.1
Please see References for further details.
Patch
please upgrade to the following versions:
Fixed on patch versions: >=3.1.2 and on major releases: >=4.0.0
Impact
pre-commit breaks when using dependency Taipy 3.1.1
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | taipy | all versions | 4.0.0pip install --upgrade 'taipy==4.0.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for taipy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update taipy to 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pp84-v3mw-gg4w 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
Is GHSA-pp84-v3mw-gg4w in your dependencies?
Find it across PyPI, including transitive dependencies.