{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-132069 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-132069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-132069 is a medium-severity vulnerability in misp, published on 18 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-132069 and fix it if it is affected.\n\nWhat it is: CVE-2026-132069 is a medium-severity vulnerability in misp, published on 18 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-132069 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-132069/ (Markdown: https://insights.sbomify.com/CVE-2026-132069/index.md)","id":"CVE-2026-132069","markdown":"https://insights.sbomify.com/CVE-2026-132069/index.md","name":"CVE-2026-132069","record":{"aliases":["GHSA-86hp-pwwm-2j34"],"analysis":null,"analysis_generated_by":null,"assigner":"CIRCL","component":null,"cpe":[{"criteria":[{"cpe":"cpe:2.3:a:misp_project:misp:*:*:*:*:*:*:*:*","source":"cna","version_end_including":"2.5.51"}],"n_criteria":1,"name":null,"product":"misp","vendor":"misp_project"}],"cvss":{"score":6.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:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"MISP (Malware Information Sharing Platform) contains an authorization bypass in the SharingGroup model's captureSGExisting method. The authorization check used a logical AND condition that effectively exempted users with the sync permission (perm_sync) from the membership verification. Specifically, the original condition 'if (!checkIfAuthorised(...) \u0026\u0026 !perm_sync) return false' meant that any user holding the sync role would pass the check regardless of whether they were actually a member of the target sharing group.\n\nA sync user who knows or can discover the UUID of a non-local sharing group could exploit this flaw through the /sharing_groups/add endpoint or by embedding a SharingGroup object in pushed sync data. The attacker could rewrite the sharing group record to add their own organisation as a member or insert an all_orgs server entry for their MISP instance, thereby gaining read access to all events contained in that group. This exposes threat intelligence data that was intended to be restricted to the group's legitimate members.\n\nThe vulnerability requires an authenticated account with the sync role and knowledge of a valid sharing group UUID. No user interaction is required. The impact is unauthorized disclosure of shared threat intelligence events and limited integrity modification of the sharing group record.","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 Authorization Bypass: Sync Users Can Modify and Read Non-Member Sharing Groups","id":"CVE-2026-132069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry","id":"CVE-2026-132079"},"nickname":null,"packages":[],"prev":{"headline":"Lldpd: lldpd: out-of-bounds read in liblldpctl on a short lldp-med location","id":"CVE-2026-132049"},"products":["misp"],"published":"2026-11-18","related":[],"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","text_fixes":[],"updated":"2026-11-18","vendor_status":[],"vendors":["misp"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-132069/"}