{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-86351 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-86351 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-86351 is a medium-severity vulnerability in Misp-Project Misp, published on 7 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-86351 and fix it if it is affected.\n\nWhat it is: CVE-2026-86351 is a medium-severity vulnerability in Misp-Project Misp, published on 7 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-86351 in the wild and no public exploit code.\n\nAffected product: Misp-Project 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-86351/ (Markdown: https://insights.sbomify.com/CVE-2026-86351/index.md)","id":"CVE-2026-86351","markdown":"https://insights.sbomify.com/CVE-2026-86351/index.md","name":"CVE-2026-86351","record":{"aliases":["GHSA-7q84-h6g5-j34g"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing","requires_auth":"low_privilege","summary":"Authenticated users can trigger open redirects via protocol-relative URLs in homepage settings, potentially facilitating phishing attacks.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[{"product":"misp","vendor":"misp-project"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Affected versions of MISP validate the user-configurable homepage by checking only whether the supplied path begins with /. That check is insufficient because protocol-relative URLs such as //attacker.example also begin with / but resolve to an external origin in browsers.\n\nThe vulnerable homepage value can be stored as a user setting and later used by the post-login routing logic. The commit explicitly identifies //attacker.example as a payload that passed validation and was emitted to the Location header after login.\n\nThe fix introduces a shared InternalRedirectValidator that rejects URLs containing a host, scheme, userinfo, unsafe leading // or /\\, malformed URLs, and control characters. It also revalidates homepage settings on read so legacy or internally written unsafe values cannot bypass the new storage-time validation.\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 User Homepage Validation Allows Authenticated Open Redirect via Protocol-Relative URL","id":"CVE-2026-86351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"misp-project:misp","products":["misp-project:misp"],"type":"open_redirect","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Update Package Framework","id":"CVE-2026-86358"},"packages":[],"prev":{"headline":"Apache Tomcat: Regression in fix for CVE-2026-41293 can trigger request header mix-up","id":"CVE-2026-86350"},"products":["MISP"],"published":"2026-09-07","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-46918","kev_date_added":null,"published":"2024-09-15"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-45509","kev_date_added":null,"published":"2024-09-01"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-29858","kev_date_added":null,"published":"2024-03-21"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-29859","kev_date_added":null,"published":"2024-03-21"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-25674","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-25675","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-50918","kev_date_added":null,"published":"2023-12-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["MISP"]},"summary":"Authenticated users can trigger open redirects via protocol-relative URLs in homepage settings, potentially facilitating phishing attacks.","url":"https://insights.sbomify.com/CVE-2026-86351/"}