{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-133163 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-133163 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-133163 is a medium-severity vulnerability in misp, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-133163 and fix it if it is affected.\n\nWhat it is: CVE-2026-133163 is a medium-severity vulnerability in misp, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-133163 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-133163/ (Markdown: https://insights.sbomify.com/CVE-2026-133163/index.md)","id":"CVE-2026-133163","markdown":"https://insights.sbomify.com/CVE-2026-133163/index.md","name":"CVE-2026-133163","record":{"aliases":["GHSA-m547-rfg3-gmf6"],"analysis":null,"analysis_generated_by":null,"assigner":"CIRCL","component":null,"cpe":[{"criteria":[{"cpe":"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*","source":"cna","version_end_including":"2.5.51"}],"n_criteria":1,"name":null,"product":"misp","vendor":"misp"}],"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:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"MISP contains an authorization bypass affecting the event protection mechanism. In MISP, a protected event is designed to be modifiable only through the events/edit endpoint with a valid cryptographic signature. However, the protection check was enforced solely on that single route. All other write endpoints that operate on an event—attributes (add, edit, delete), objects (delete), events (populate, publish, unprotect, upload_sample, upload_analysis_file), tags (attach, detach), event reports (edit, delete), galaxy clusters (attach, detach), and cryptographic keys (add, delete)—lacked the equivalent check.\n\nAs a result, an authenticated user holding the sync permission (perm_sync) who is neither a site administrator nor an internal sync user (perm_sync_internal), and who belongs to the same organization as the event's creator (orgc_id), could modify, delete, or add data to a protected event without providing a valid signature. This included the ability to unprotect the event entirely, publish it to other instances, and add cryptographic signing keys that would subsequently permit signed edits, effectively nullifying the protection mechanism.\n\nThe vulnerability requires an authenticated sync user account within the event's creator organization. No user interaction or special network conditions are required; standard API calls to the affected endpoints are sufficient. The security impact is a loss of integrity over protected threat-intelligence events: an attacker can inject, alter, or remove attributes, objects, tags, reports, and galaxy cluster associations, and can remove the protection flag or add signing keys to enable persistent unauthorized modification.","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: External Sync User Can Modify Protected Events Without Signature via Multiple Write Routes","id":"CVE-2026-133163","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":"MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass","id":"CVE-2026-133165"},"nickname":null,"packages":[],"prev":{"headline":"Harness `ToolOutputLimits` ANSI stripping can take quadratic time, blocking the event loop","id":"CVE-2026-133161"},"products":["misp"],"published":"2026-11-19","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-19","vendor_status":[],"vendors":["misp"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-133163/"}