{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90957 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-90957 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-90957 is a medium-severity cross-site scripting vulnerability in MISP, published on 14 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-90957 and fix it if it is affected.\n\nWhat it is: CVE-2026-90957 is a medium-severity cross-site scripting vulnerability in MISP, published on 14 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-90957 in the wild and no public exploit code.\n\nAffected product: MISP. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-90957/ (Markdown: https://insights.sbomify.com/CVE-2026-90957/index.md)","id":"CVE-2026-90957","markdown":"https://insights.sbomify.com/CVE-2026-90957/index.md","name":"CVE-2026-90957","record":{"aliases":["GHSA-5mp5-7f8h-r69q"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing platform","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts on the MISP origin via malicious SVG files, potentially stealing user sessions and data.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"Affected versions of MISP serve uploaded SVG images inline without a restrictive browser sandbox.\n\nThe commit explains that SVG files are XML documents rather than passive bitmap images. While scripts inside SVG do not execute when the SVG is rendered through a normal \u003cimg\u003e, they can execute when the SVG is navigated to directly or embedded as a document. In that case, malicious \u003cscript\u003e elements, event handlers, or javascript: URLs execute on the MISP origin with the viewer’s session.\n\nThe affected use cases include:\n\n - organisation SVG logos;\n - event-report SVG pictures.\n\nImportantly, the vulnerable behavior is on the serve path, not merely the upload path: the patch notes that a malicious SVG uploaded while SVG support was enabled could remain dangerous even after uploads were later disabled.\n\nVersion affected: ≤2.5.45","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MISP: Stored XSS via Inline-Served SVG Organisation Logos and Report Pictures","id":"CVE-2026-90957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in Red Hat Ansible Automation Platform 2","id":"CVE-2026-90959"},"packages":[],"prev":{"headline":"MISP CLI Shell Audit Logs Lose User Identity and CLI Marker After First Lazy Model Load","id":"CVE-2026-90955"},"products":["MISP"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-14","vendors":["MISP"]},"summary":"Attackers can execute arbitrary scripts on the MISP origin via malicious SVG files, potentially stealing user sessions and data.","url":"https://insights.sbomify.com/CVE-2026-90957/"}