{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-95754 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-95754 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-95754 is a medium-severity authentication bypass vulnerability in MISP, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-95754 and fix it if it is affected.\n\nWhat it is: CVE-2026-95754 is a medium-severity authentication bypass vulnerability in MISP, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-95754 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-95754/ (Markdown: https://insights.sbomify.com/CVE-2026-95754/index.md)","id":"CVE-2026-95754","markdown":"https://insights.sbomify.com/CVE-2026-95754/index.md","name":"CVE-2026-95754","record":{"aliases":["GHSA-w52q-73m7-hm7j"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing","requires_auth":"none","summary":"Disabled users with TOTP enabled could bypass initial rejection, receiving a TOTP prompt instead of immediate denial, though final authentication still failed.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"In MISP's UsersController login() method, the pre-authentication database query used for the TOTP (two-factor authentication) verification branch did not include the User.disabled column in its SELECT fields list. The query selected only User.password, User.totp, and User.hotp_counter. When the TOTP branch subsequently accessed $unauth_user['User']['disabled'], the key was absent from the result set, producing a PHP 'Undefined array key' warning and causing the expression to evaluate as null (falsy). As a result, the disabled-user guard in the TOTP branch was effectively a no-op: a disabled, TOTP-enrolled user could proceed to the TOTP verification step rather than being rejected at that point. \n\nThe commit message explicitly states this was 'harmless in practice' because the subsequent identify() call re-validates the user and would still reject a disabled account. \n\nThe practical security impact is therefore minimal, limited to a very small information-disclosure difference in the login response (a TOTP prompt is presented instead of an immediate rejection) and a PHP warning in application logs.","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: Disabled-user check ineffective in pre-authentication TOTP login branch","id":"CVE-2026-95754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MISP ACLComponent: Typo in previewEventAttributes ACL key bypasses intended access restriction","id":"CVE-2026-95805"},"packages":[],"prev":{"headline":"Authenticated Local Memory Corruption Vulnerability in AOS-8 Web-Based Management Interface","id":"CVE-2026-95721"},"products":["MISP"],"published":"2026-09-22","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["MISP"]},"summary":"Disabled users with TOTP enabled could bypass initial rejection, receiving a TOTP prompt instead of immediate denial, though final authentication still failed.","url":"https://insights.sbomify.com/CVE-2026-95754/"}