{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54397 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54397 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54397 is a medium-severity missing authorization vulnerability in misp, published on 12 Jun 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-54397 and fix it if it is affected.\n\nWhat it is: CVE-2026-54397 is a medium-severity missing authorization vulnerability in misp, published on 12 Jun 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-54397 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-54397/ (Markdown: https://insights.sbomify.com/CVE-2026-54397/index.md)","id":"CVE-2026-54397","markdown":"https://insights.sbomify.com/CVE-2026-54397/index.md","name":"CVE-2026-54397","record":{"aliases":["GHSA-4qr4-pqwx-m352"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing","requires_auth":"low_privilege","summary":"Authenticated users can bypass authorization checks to assign events to unauthorized sharing groups, leading to information disclosure and metadata modification.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":6.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:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"A vulnerability in MISP’s non-REST event editing path allowed an authenticated user with event edit permissions to manipulate the submitted form data and set an event’s sharing_group_id to a sharing group they were not authorized to use. When distribution was set to sharing group distribution, the non-REST save path accepted the submitted sharing_group_id without performing the same sharing group authorization check enforced by the REST edit path.\n\nAn attacker could exploit this by tampering with the event edit request and assigning an event to an undisclosed or unauthorized sharing group. This could result in unauthorized use of restricted sharing groups, disclosure of the sharing group name in event listings, and unintended modification of the event’s distribution metadata.\n\nThe issue is fixed by validating that the selected sharing group can be used by the current user when the sharing group is changed, and by clearing sharing_group_id when the event distribution is not set to sharing group distribution.","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 editing allows unauthorized assignment to undisclosed sharing groups","id":"CVE-2026-54397","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":"MISP object edit authorization bypass allows unauthorized sharing group assignment","id":"CVE-2026-54398"},"packages":[],"prev":{"headline":"MISP AuthKey edit endpoint allows authenticated user email enumeration","id":"CVE-2026-54396"},"products":["misp"],"published":"2026-06-12","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-06-15","vendors":["misp"]},"summary":"Authenticated users can bypass authorization checks to assign events to unauthorized sharing groups, leading to information disclosure and metadata modification.","url":"https://insights.sbomify.com/CVE-2026-54397/"}