What is CVE-2026-7142?

CVE-2026-7142 is a low-severity security vulnerability in wooey (pip), affecting versions < 0.13.3rc1. It is fixed in 0.13.3rc1.

How severe is CVE-2026-7142?

CVE-2026-7142 has a CVSS score of 6.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of wooey are affected by CVE-2026-7142?

wooey (pip) versions < 0.13.3rc1 is affected.

Is there a fix for CVE-2026-7142?

Yes. CVE-2026-7142 is fixed in 0.13.3rc1. Upgrade to this version or later.

Is CVE-2026-7142 exploitable, and should I be worried?

Whether CVE-2026-7142 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.

What actually determines whether CVE-2026-7142 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.

CVE-2026-7142 in wooey

Q: How severe is CVE-2026-7142?

CVE-2026-7142 has a CVSS score of 6.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of wooey are affected by CVE-2026-7142?

wooey (pip) versions < 0.13.3rc1 is affected.

Q: Is there a fix for CVE-2026-7142?

Yes. CVE-2026-7142 is fixed in 0.13.3rc1. Upgrade to this version or later.

Q: Is CVE-2026-7142 exploitable, and should I be worried?

Whether CVE-2026-7142 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.

Q: What actually determines whether CVE-2026-7142 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.

Q: How do I fix CVE-2026-7142?

Upgrade wooey to 0.13.3rc1 or later.

Summary

Wooey has an Incorrect Privilege Assignment issue

A vulnerability was determined in Wooey up to 0.13.2. The impacted element is the function add_or_update_script of the file wooey/api/scripts.py of the component API Endpoint. Executing a manipulation can lead to improper authorization. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 0.13.3rc1 and 0.14.0 is sufficient to resolve this issue. This patch is called f7846fc0c323da8325422cab32623491757f1b88. The affected component should be upgraded.

Impact

CVE-2026-7142 has a CVSS score of 6.3 (Low). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.13.3rc1); upgrading removes the vulnerable code path.

Affected versions

wooey (< 0.13.3rc1)

Security releases

wooey → 0.13.3rc1 (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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade wooey to 0.13.3rc1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-7142? CVE-2026-7142 is a low-severity security vulnerability in wooey (pip), affecting versions < 0.13.3rc1. It is fixed in 0.13.3rc1.
How severe is CVE-2026-7142? CVE-2026-7142 has a CVSS score of 6.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of wooey are affected by CVE-2026-7142? wooey (pip) versions < 0.13.3rc1 is affected.
Is there a fix for CVE-2026-7142? Yes. CVE-2026-7142 is fixed in 0.13.3rc1. Upgrade to this version or later.
Is CVE-2026-7142 exploitable, and should I be worried? Whether CVE-2026-7142 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
What actually determines whether CVE-2026-7142 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.
How do I fix CVE-2026-7142? Upgrade wooey to 0.13.3rc1 or later.