What is GHSA-pp84-v3mw-gg4w?

### 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 =3.1.2 and on major releases: >=4.0.0 ### Impact pre-commit breaks when using dependency Taipy 3.1.1

How severe is GHSA-pp84-v3mw-gg4w?

No CVSS score has been assigned to GHSA-pp84-v3mw-gg4w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pp84-v3mw-gg4w?

GHSA-pp84-v3mw-gg4w affects the following packages: taipy (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-pp84-v3mw-gg4w?

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.

How do I detect GHSA-pp84-v3mw-gg4w in my PyPI dependencies?

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.

How do I mitigate GHSA-pp84-v3mw-gg4w 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.

How does O3 Security protect against GHSA-pp84-v3mw-gg4w?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pp84-v3mw-gg4w can be triaged on real exposure rather than presence alone.

Is GHSA-pp84-v3mw-gg4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-pp84-v3mw-gg4w 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.

When was GHSA-pp84-v3mw-gg4w published, and has it been updated?

GHSA-pp84-v3mw-gg4w was published on August 27, 2024 and was last updated on November 30, 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

GHSA-pp84-v3mw-gg4w — taipy

GHSA-pp84-v3mw-gg4w is a security vulnerability in taipy. A fix is available for taipy — see the affected versions and patch details below.

Taipy 3.1.1 affected by CVEs on flask-core and pymongo

Published

Aug 27, 2024

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 30, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍taipy

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

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`taipy`	all versions	4.0.0`pip install --upgrade 'taipy==4.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 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pp84-v3mw-gg4w can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pp84-v3mw-gg4w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-pp84-v3mw-gg4w in your dependencies?

O3 Security finds GHSA-pp84-v3mw-gg4w across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works