{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103858 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103858 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103858 is a medium-severity missing authorization vulnerability in MISP, published on 1 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-103858 and fix it if it is affected.\n\nWhat it is: CVE-2026-103858 is a medium-severity missing authorization vulnerability in MISP, published on 1 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-103858 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-103858/ (Markdown: https://insights.sbomify.com/CVE-2026-103858/index.md)","id":"CVE-2026-103858","markdown":"https://insights.sbomify.com/CVE-2026-103858/index.md","name":"CVE-2026-103858","record":{"aliases":["GHSA-vwhj-wmrx-p88c"],"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 read and post to restricted MISP discussion threads due to incomplete authorization checks, exposing sensitive data and allowing unauthorized content injection.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"MISP contains an incomplete authorization check in the discussion posting functionality. When a user submits a post to a thread or replies to an existing post, the application only verified whether the target thread was restricted to a single organization (org-only distribution). It did not enforce the full thread access control list, including sharing-group membership and event-level visibility.\n\nAs a result, an authenticated user who is outside the relevant sharing group or who does not have visibility on the associated event could:\n\n- Read the thread title and the content of the quoted post\n\n- Submit a new post into the discussion thread\n\nThis constitutes both an information disclosure (reading restricted thread and post content) and an integrity issue (injecting content into a thread the user is not authorized to participate in).\n\nAffected: \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 Incomplete Thread Authorization Allows Unauthorized Read and Post Access to Discussions","id":"CVE-2026-103858","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":"Pulp-container: registry credentials are reused across remotes in a worker","id":"CVE-2026-103868"},"packages":[],"prev":{"headline":"Adobe Framemaker | Out-of-bounds Read (CWE-125)","id":"CVE-2026-103857"},"products":["MISP"],"published":"2026-10-01","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-01","vendors":["MISP"]},"summary":"Authenticated users can read and post to restricted MISP discussion threads due to incomplete authorization checks, exposing sensitive data and allowing unauthorized content injection.","url":"https://insights.sbomify.com/CVE-2026-103858/"}