{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-88915 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-88915 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-88915 is a high-severity missing authorization vulnerability in MISP, published on 10 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-88915 and fix it if it is affected.\n\nWhat it is: CVE-2026-88915 is a high-severity missing authorization vulnerability in MISP, published on 10 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-88915 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-88915/ (Markdown: https://insights.sbomify.com/CVE-2026-88915/index.md)","id":"CVE-2026-88915","markdown":"https://insights.sbomify.com/CVE-2026-88915/index.md","name":"CVE-2026-88915","record":{"aliases":["GHSA-46cw-r5cx-57f2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing","requires_auth":"low_privilege","summary":"Attackers can bypass sharing group and tagging authorization checks when instantiating MISP event templates, potentially exposing restricted data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Affected versions of MISP do not consistently enforce the acting user's authorization when instantiating event templates.\n\nFor templates using distribution = 4, the template can specify a sharing_group_id. The instantiation path passed that value into event creation without verifying that the user instantiating the template was actually permitted to use the selected sharing group. The commit notes that Event::_add() only performed its own sharing-group authorization in another code path, leaving template instantiation able to write the identifier directly.\n\nThe same instantiation path also attached template-specified tags without checking the user's normal tagging permissions. In addition, it hardcoded local =\u003e 0, meaning tags marked local_only could be attached globally and consequently propagate through synchronization or export, contrary to their intended restriction.\n\nThe fix adds explicit SharingGroup::canUse() authorization for the acting user, applies the same tag-modification checks used by normal event tagging, and ensures local_only tags are attached locally.\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 Event Template Instantiation Bypasses Sharing Group and Tagging Authorization","id":"CVE-2026-88915","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Admin Access Bypass via Header Fallback in TÜBİTAK ULAKBİM's UlakPDF","id":"CVE-2026-88916"},"packages":[],"prev":{"headline":"Gstreamer1-plugins-good: gstreamer: integer overflow and out-of-bounds read in qtdemux cea-608 closed-caption parser","id":"CVE-2026-88914"},"products":["MISP"],"published":"2026-09-10","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-10","vendors":["MISP"]},"summary":"Attackers can bypass sharing group and tagging authorization checks when instantiating MISP event templates, potentially exposing restricted data.","url":"https://insights.sbomify.com/CVE-2026-88915/"}