{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-133175 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-133175 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-133175 is a medium-severity vulnerability in misp, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-133175 and fix it if it is affected.\n\nWhat it is: CVE-2026-133175 is a medium-severity vulnerability in misp, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-133175 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-133175/ (Markdown: https://insights.sbomify.com/CVE-2026-133175/index.md)","id":"CVE-2026-133175","markdown":"https://insights.sbomify.com/CVE-2026-133175/index.md","name":"CVE-2026-133175","record":{"aliases":["GHSA-xjg3-x7m3-2h97"],"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":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"MISP contains an authorization bypass in its server-to-server proposal synchronization mechanism. Two related flaws were identified:\n\n1. The events/pushProposals endpoint located the target event by UUID without enforcing any access-control check. A sync user with perm_sync could push shadow-attribute proposals to any event on the local instance, including events with restricted distribution (e.g., distribution level 0, visible only to the owning organisation). The stored proposal also carried the sender-supplied event_uuid and event_org_id rather than the local event's actual identity, corrupting the data model.\n\n2. When accepting an edit proposal (old_id != 0), the code resolved the target live attribute by UUID alone (Attribute.uuid = shadow.uuid) without scoping the lookup to the proposal's own event. A malicious sync user could therefore craft a proposal whose uuid matched an attribute in a different event; upon acceptance, the wrong attribute would be modified or deleted. The same unscoped lookup existed in the ShadowAttribute::acceptProposal path.\n\nPreconditions: an authenticated user with sync permission (perm_sync) on a MISP instance that participates in server-to-server synchronisation. The attacker must know or enumerate the UUID of a target event or attribute.\n\nSecurity impact: unauthorised read access to restricted events, unauthorised insertion of proposals onto events the user cannot see, and unauthorised modification or deletion of attributes belonging to other events. This compromises the confidentiality and integrity of threat-intelligence data across organisational boundaries within a MISP deployment.","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 Missing Authorization in Sync Proposal Endpoints Allows Cross-Event Data Access and Modification","id":"CVE-2026-133175","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: Insufficient Authorization Allows Sync Users and External Feeds to Overwrite Organisation Details","id":"CVE-2026-133177"},"nickname":null,"packages":[],"prev":{"headline":"HotGo 2.18.6 through 2.19.0 Missing Authorization via pullMessages Endpoint","id":"CVE-2026-133174"},"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-133175/"}