{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-86417 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-86417 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-86417 is a medium-severity vulnerability in Misp-Project Misp, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-86417 and fix it if it is affected.\n\nWhat it is: CVE-2026-86417 is a medium-severity vulnerability in Misp-Project Misp, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-86417 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-86417/ (Markdown: https://insights.sbomify.com/CVE-2026-86417/index.md)","id":"CVE-2026-86417","markdown":"https://insights.sbomify.com/CVE-2026-86417/index.md","name":"CVE-2026-86417","record":{"aliases":["GHSA-82w9-ppqv-p5c6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing","requires_auth":"low_privilege","summary":"Authenticated users can retrieve template owners' email addresses via the REST API, bypassing intended visibility restrictions in MISP.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[{"product":"misp","vendor":"misp-project"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Affected versions of MISP inconsistently enforced email-address visibility in DashboardsController::listTemplates().\n\nThe query always fetched User.email, while redaction happened only inside the non-REST rendering branch. As a result, the same authenticated user who saw redacted data in the normal HTML interface could request the REST/JSON representation and receive template owners’ email addresses without the intended privilege check.\n\nThe fix moves the decision to a centralized User::canSeeEmails() authorization helper. Email addresses are now fetched only when the requester is a site administrator or the instance explicitly enables Security.disclose_user_emails. The same helper is also reused by other dashboard widgets to keep email-disclosure policy consistent.\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 Dashboard Template REST API Exposes Template Owner Email Addresses to Unauthorized Users","id":"CVE-2026-86417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"misp-project:misp","products":["misp-project:misp"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MISP Dashboard Organisation Picker Exposes Hidden Organisation Metadata to Unauthorized Users","id":"CVE-2026-86418"},"packages":[],"prev":{"headline":"ILIAS before 9.23, 10.11, and 11.4 Missing Authorization in Group Object Action Methods","id":"CVE-2026-86416"},"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 retrieve template owners' email addresses via the REST API, bypassing intended visibility restrictions in MISP.","url":"https://insights.sbomify.com/CVE-2026-86417/"}