CVE-2026-40110

CVE-2026-40110 is a high-severity security vulnerability in jupyter-server (pip), affecting versions <= 2.17.0. It is fixed in 2.18.0.

Summary

Jupyter Server uses re.match() to validate the Origin header against the allow_origin_pat configuration.

Since re.match() only anchors at the start of the string, an attacker who controls a domain like http://trusted.example.com.evil.com/ passes validation against a pattern intended to match only trusted.example.com.

Workarounds

Wrap your allow_origin_pat value with ^ and $

References

https://github.com/jupyter-server/jupyter_server/pull/603
https://docs.python.org/3/library/re.html#re.fullmatch
https://docs.python.org/3/library/re.html#re.match

Impact

<=2.17.0

Affected versions

jupyter-server (<= 2.17.0)

Security releases

jupyter-server → 2.18.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.

See it in your environment

Remediation advice

057869a327c46730afede3eab0ca2d2e3e74acea, 49b34392feaa97735b3b777e3baf8f22f2a14ed8

Frequently Asked Questions

  1. What is CVE-2026-40110? CVE-2026-40110 is a high-severity security vulnerability in jupyter-server (pip), affecting versions <= 2.17.0. It is fixed in 2.18.0.
  2. Which versions of jupyter-server are affected by CVE-2026-40110? jupyter-server (pip) versions <= 2.17.0 is affected.
  3. Is there a fix for CVE-2026-40110? Yes. CVE-2026-40110 is fixed in 2.18.0. Upgrade to this version or later.
  4. Is CVE-2026-40110 exploitable, and should I be worried? Whether CVE-2026-40110 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 CVE-2026-40110 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 CVE-2026-40110? Upgrade jupyter-server to 2.18.0 or later.

Other vulnerabilities in jupyter-server

CVE-2026-44727CVE-2026-40934CVE-2026-40110CVE-2025-61669CVE-2023-49080

Stop the waste.
Protect your environment with Kodem.