{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107175 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-107175 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-107175 is a medium-severity vulnerability in MISP, published on 7 Oct 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-107175 and fix it if it is affected.\n\nWhat it is: CVE-2026-107175 is a medium-severity vulnerability in MISP, published on 7 Oct 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-107175 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-107175/ (Markdown: https://insights.sbomify.com/CVE-2026-107175/index.md)","id":"CVE-2026-107175","markdown":"https://insights.sbomify.com/CVE-2026-107175/index.md","name":"CVE-2026-107175","record":{"aliases":["GHSA-9v45-rw9g-683m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat intelligence","requires_auth":"low_privilege","summary":"Authenticated users can cause stale correlations to persist after changing event distribution, leading to unintended information disclosure to broader sharing groups.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"MISP contains a defect in its event save workflow that prevents the correlation engine from recalculating correlations when an event's distribution level or sharing group is modified.\n\nWhen a user edits an existing event and changes its distribution or sharing_group_id, the internal before-save hook stored the incoming (new) data rather than the previously persisted values. As a result, the after-save comparison that determines whether a correlation refresh is needed never detected the change, and stale correlations persisted.\n\nSecurity impact:\n\n- Stale correlations may continue to expose event data to users in a broader sharing group after the event has been moved to a more restrictive group, resulting in unintended information disclosure.\n\n- Conversely, newly relevant correlations may not appear after a distribution widening, degrading the completeness of threat intelligence sharing.\n\nPreconditions:\n\n- An authenticated user with write access to at least one MISP event.\n\n- The user modifies the event's distribution or sharing_group_id field.\n\nAffected versions: \u003c2.5.48","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 Correlation Engine Fails to Refresh When Event Distribution or Sharing Group Changes","id":"CVE-2026-107175","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cluster-samples-operator: role reads all secrets in openshift-config, not just pull-secret","id":"CVE-2026-107176"},"packages":[],"prev":{"headline":"Source-to-image: source-to-image: security boundary bypass via absolute symbolic link extraction","id":"CVE-2026-107174"},"products":["MISP"],"published":"2026-10-07","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-10-07","vendors":["MISP"]},"summary":"Authenticated users can cause stale correlations to persist after changing event distribution, leading to unintended information disclosure to broader sharing groups.","url":"https://insights.sbomify.com/CVE-2026-107175/"}