What is CVE-2022-39286?

CVE-2022-39286 is a high-severity improper privilege management vulnerability in jupyter-core (pip), affecting versions < 4.11.2. It is fixed in 4.11.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.

How severe is CVE-2022-39286?

CVE-2022-39286 has a CVSS score of 8.8 (High). 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 jupyter-core are affected by CVE-2022-39286?

jupyter-core (pip) versions < 4.11.2 is affected.

Is there a fix for CVE-2022-39286?

Yes. CVE-2022-39286 is fixed in 4.11.2. Upgrade to this version or later.

Is CVE-2022-39286 exploitable, and should I be worried?

Whether CVE-2022-39286 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-2022-39286 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-2022-39286?

Upgrade jupyter-core to 4.11.2 or later.

CVE-2022-39286 in jupyter-core

Q: How severe is CVE-2022-39286?

CVE-2022-39286 has a CVSS score of 8.8 (High). 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 jupyter-core are affected by CVE-2022-39286?

jupyter-core (pip) versions < 4.11.2 is affected.

Q: Is there a fix for CVE-2022-39286?

Yes. CVE-2022-39286 is fixed in 4.11.2. Upgrade to this version or later.

Q: Is CVE-2022-39286 exploitable, and should I be worried?

Whether CVE-2022-39286 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-2022-39286 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-2022-39286?

Upgrade jupyter-core to 4.11.2 or later.

Summary

Execution with Unnecessary Privileges in JupyterApp

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?
No

References

Are there any links users can visit to find out more?
Similar advisory in IPython

Impact

What kind of vulnerability is it? Who is impacted?
We’d like to disclose an arbitrary code execution vulnerability in jupyter_core that stems from jupyter_core executing untrusted files in the current working directory. This vulnerability allows one user to run code as another.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2022-39286 has a CVSS score of 8.8 (High). 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 (4.11.2); upgrading removes the vulnerable code path.

Affected versions

jupyter-core (< 4.11.2)

Security releases

jupyter-core → 4.11.2 (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

Has the problem been patched? What versions should users upgrade to?
Users should upgrade to jupyter_core>=4.11.2.

Frequently Asked Questions

What is CVE-2022-39286? CVE-2022-39286 is a high-severity improper privilege management vulnerability in jupyter-core (pip), affecting versions < 4.11.2. It is fixed in 4.11.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
How severe is CVE-2022-39286? CVE-2022-39286 has a CVSS score of 8.8 (High). 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 jupyter-core are affected by CVE-2022-39286? jupyter-core (pip) versions < 4.11.2 is affected.
Is there a fix for CVE-2022-39286? Yes. CVE-2022-39286 is fixed in 4.11.2. Upgrade to this version or later.
Is CVE-2022-39286 exploitable, and should I be worried? Whether CVE-2022-39286 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-2022-39286 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-2022-39286? Upgrade jupyter-core to 4.11.2 or later.