GHSA-PP84-V3MW-GG4W

GHSA-PP84-V3MW-GG4W is a high-severity security vulnerability in taipy (pip), affecting versions <= 3.1.1. It is fixed in 4.0.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Taipy 3.1.1 affected by CVEs on flask-core and pymongo

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.

Impact

pre-commit breaks when using dependency Taipy 3.1.1

Affected versions

taipy (<= 3.1.1)

Security releases

taipy → 4.0.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

please upgrade to the following versions:

Fixed on patch versions: >=3.1.2
and on major releases: >=4.0.0

Frequently Asked Questions

  1. What is GHSA-PP84-V3MW-GG4W? GHSA-PP84-V3MW-GG4W is a high-severity security vulnerability in taipy (pip), affecting versions <= 3.1.1. It is fixed in 4.0.0.
  2. Which versions of taipy are affected by GHSA-PP84-V3MW-GG4W? taipy (pip) versions <= 3.1.1 is affected.
  3. Is there a fix for GHSA-PP84-V3MW-GG4W? Yes. GHSA-PP84-V3MW-GG4W is fixed in 4.0.0. Upgrade to this version or later.
  4. Is GHSA-PP84-V3MW-GG4W exploitable, and should I be worried? Whether GHSA-PP84-V3MW-GG4W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-PP84-V3MW-GG4W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-PP84-V3MW-GG4W? Upgrade taipy to 4.0.0 or later.

Other vulnerabilities in taipy

Stop the waste.
Protect your environment with Kodem.