{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-94381 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-94381 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-94381 is a high-severity vulnerability in MISP, published on 21 Sep 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-94381 and fix it if it is affected.\n\nWhat it is: CVE-2026-94381 is a high-severity vulnerability in MISP, published on 21 Sep 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-94381 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-94381/ (Markdown: https://insights.sbomify.com/CVE-2026-94381/index.md)","id":"CVE-2026-94381","markdown":"https://insights.sbomify.com/CVE-2026-94381/index.md","name":"CVE-2026-94381","record":{"aliases":["GHSA-mw89-3hh7-vfpg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing platform","requires_auth":"low_privilege","summary":"Attackers with read-only API keys can regain full account permissions via updateLoginTime, bypassing API restrictions to perform unauthorized actions.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"MISP has a security issue that can let a user gain more access than their API key is supposed to allow.\n\nA read-only API key should only let someone view information. However, after logging in with such a key, a specific MISP function could accidentally restore the user’s normal account permissions. This means someone with a read-only API key could potentially gain write, delete, or even administrator access if their underlying account has those permissions.\n\nExploiting the issue requires a valid read-only API key and a single request to the affected function.\n\nThe main impact is that MISP’s API key restrictions can be bypassed, allowing actions that the API key was specifically meant to prevent.\n\nVersion affected: \u003c2.5.47","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 Privilege Escalation: Read-Only API Key User Can Regain Full Role via updateLoginTime","id":"CVE-2026-94381","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Beszel before 0.19.0 Insecure Direct Object Reference via user-alerts","id":"CVE-2026-94382"},"packages":[],"prev":{"headline":"Host Header Injection in HAVELSAN's Liman MYS","id":"CVE-2026-94380"},"products":["MISP"],"published":"2026-09-21","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":"total"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["MISP"]},"summary":"Attackers with read-only API keys can regain full account permissions via updateLoginTime, bypassing API restrictions to perform unauthorized actions.","url":"https://insights.sbomify.com/CVE-2026-94381/"}