{"answers":{"affected":"3 open source packages ship an affected version, including jupyter-server. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6657 exists.","fix":"No fix has been published for CVE-2026-6657 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6657 is a medium-severity vulnerability in jupyter/jupyter, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-6657 and fix it if it is affected.\n\nWhat it is: CVE-2026-6657 is a medium-severity vulnerability in jupyter/jupyter, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6657 exists.\n\nAffected packages and fixed versions:\n- jupyter-server (PyPI): affected from 1.12.0 up to 2.17.0; no fix listed\n- jupyter-server (PyPI): affected from 1.12.0 up to 2.17.0; no fix listed\n- jupyter-server (PyPI): affected from 1.12.0 up to 2.17.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-6657/ (Markdown: https://insights.sbomify.com/CVE-2026-6657/index.md)","id":"CVE-2026-6657","markdown":"https://insights.sbomify.com/CVE-2026-6657/index.md","name":"CVE-2026-6657","record":{"aliases":["DEBIAN-CVE-2026-6657","GHSA-v42x-x7jp-845h","PYSEC-2026-3472","UBUNTU-CVE-2026-6657"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Jupyter server","requires_auth":"none","summary":"Attackers can bypass CORS validation in Jupyter Server when using regex patterns, enabling phishing, code execution, and data theft.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"jupyter_server","vendor":"jupyter"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"A vulnerability in jupyter-server versions 1.12.0 through 2.17.0 allows an attacker to bypass CORS origin validation when the `allow_origin_pat` configuration is used. The issue arises from the use of `re.match()` for validating the `Origin` header, which only anchors at the start of the string. This allows attacker-controlled domains such as `trusted.example.com.evil.com` to pass validation against patterns intended to match `trusted.example.com`. The vulnerability affects multiple locations in the codebase, including CORS headers, WebSocket connections, referer validation, and login redirects, potentially enabling phishing attacks, arbitrary code execution, and unauthorized access to sensitive API responses.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"CORS Origin Validation Bypass in jupyter-server","id":"CVE-2026-6657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Cross-site Scripting (XSS) in jupyter/nbconvert","id":"CVE-2026-6658"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["1.12.0"],"last_affected":["2.17.0"],"package":"jupyter-server","purl":null,"source":"GHSA-v42x-x7jp-845h"},{"ecosystem":"PyPI","fixed":[],"introduced":["1.12.0"],"last_affected":["2.17.0"],"package":"jupyter-server","purl":"pkg:pypi/jupyter-server","source":"GHSA-v42x-x7jp-845h"},{"ecosystem":"PyPI","fixed":[],"introduced":["1.12.0"],"last_affected":["2.17.0"],"package":"jupyter-server","purl":"pkg:pypi/jupyter-server","source":"PYSEC-2026-3472"}],"prev":{"headline":"Crypt::Password versions through 0.28 for Perl are susceptible to timing attacks","id":"CVE-2026-6656"},"products":["jupyter/jupyter"],"published":"2026-06-03","related":[{"cvss_score":9.3,"headline":"Jupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSP","id":"CVE-2026-44727","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":7.6,"headline":"jupyter-server path traversal allows access to sibling directories sharing root_dir name prefix","id":"CVE-2026-35397","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.6,"headline":"jupyter-server CORS origin validation bypass via unanchored regex in allow_origin_pat","id":"CVE-2026-40110","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.6,"headline":"jupyter-server authentication cookies remain valid after password reset due to static cookie secret","id":"CVE-2026-40934","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.5,"headline":"Jupyter server on Windows discloses Windows user password hash","id":"CVE-2024-35178","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":7.5,"headline":"Sensitive Auth \u0026 Cookie data stored in Jupyter server logs","id":"CVE-2022-24757","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.1,"headline":"Known or guessable hidden files may be accessed in Jupyter Server","id":"CVE-2022-29241","kev_date_added":null,"published":"2022-06-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-03","vendors":["jupyter"]},"summary":"Attackers can bypass CORS validation in Jupyter Server when using regex patterns, enabling phishing, code execution, and data theft.","url":"https://insights.sbomify.com/CVE-2026-6657/"}