{"answers":{"affected":"2 open source packages ship an affected version, including mercury.","exploited":"There is no known exploitation of CVE-2026-111059 in the wild and no public exploit code.","fix":"Upgrade mercury to 3.2.11 or later.","what":"CVE-2026-111059 is a medium-severity cross-site scripting vulnerability in mljar mercury, published on 19 Oct 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-111059 and fix it if it is affected.\n\nWhat it is: CVE-2026-111059 is a medium-severity cross-site scripting vulnerability in mljar mercury, published on 19 Oct 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: There is no known exploitation of CVE-2026-111059 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mercury (PyPI): affected from 3.0.0; fixed in 3.2.11\n- mercury (PyPI): affected from 3.0.0; fixed in 3.2.11\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-111059/ (Markdown: https://insights.sbomify.com/CVE-2026-111059/index.md)","id":"CVE-2026-111059","markdown":"https://insights.sbomify.com/CVE-2026-111059/index.md","name":"CVE-2026-111059","record":{"aliases":["GHSA-2658-85cv-9wwq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python notebook framework","requires_auth":"none","summary":"Attackers can inject malicious scripts via Markdown content in Mercury applications, leading to code execution in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Mercury is a Python framework for sharing Jupyter notebooks as web applications and dashboards. From 3.0.0 until 3.2.11, mr.Markdown converts attacker-controlled Markdown to HTML without sanitizing raw HTML before assigning it to an ipywidgets.HTML sink. Event-handler attributes and other active HTML can therefore reach the DOM and execute when another user views the application. This issue is fixed in version 3.2.11.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Mercury: Stored / DOM Cross-Site Scripting (XSS): mr.Markdown renders untrusted content as raw, unsanitized HTML","id":"CVE-2026-111059","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"russh agent server converts constraint records into unbounded never-rolled-back tasks","id":"CVE-2026-111061"},"packages":[{"ecosystem":"PyPI","fixed":["3.2.11"],"introduced":["3.0.0"],"last_affected":[],"package":"mercury","purl":null,"source":"GHSA-2658-85cv-9wwq"},{"ecosystem":"PyPI","fixed":["3.2.11"],"introduced":["3.0.0"],"last_affected":[],"package":"mercury","purl":"pkg:pypi/mercury","source":"GHSA-2658-85cv-9wwq"}],"prev":{"headline":"Mercury: Unauthenticated Remote Code Execution via /api/kernels","id":"CVE-2026-111058"},"products":["mercury"],"published":"2026-10-19","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["mljar"]},"summary":"Attackers can inject malicious scripts via Markdown content in Mercury applications, leading to code execution in victim browsers.","url":"https://insights.sbomify.com/CVE-2026-111059/"}