{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-56425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56425 is a critical authentication bypass vulnerability in Misp-Project Misp, published on 22 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-56425 and fix it if it is affected.\n\nWhat it is: CVE-2026-56425 is a critical authentication bypass vulnerability in Misp-Project Misp, published on 22 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-56425 in the wild and no public exploit code.\n\nAffected product: Misp-Project 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-56425/ (Markdown: https://insights.sbomify.com/CVE-2026-56425/index.md)","id":"CVE-2026-56425","markdown":"https://insights.sbomify.com/CVE-2026-56425/index.md","name":"CVE-2026-56425","record":{"aliases":["GHSA-ch28-mjgc-m4wr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP AAD plugin","requires_auth":"low_privilege","summary":"Attackers can hijack sessions or bypass OAuth security via weak state handling and missing session rotation in the MISP AAD authentication plugin.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[{"product":"misp","vendor":"misp-project"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"description":"The Azure Active Directory (AAD) authentication implementation contained multiple weaknesses in its OAuth 2.0 authorization flow that could allow attackers to bypass important security guarantees provided by the protocol.\n\nThe application used the PHP session identifier (session_id()) as the OAuth state parameter. Because session identifiers are long-lived authentication credentials, exposing them in OAuth redirect URLs could leak valid session tokens through browser history, HTTP Referer headers, reverse proxies, access logs, or third-party infrastructure involved in the authentication flow. If obtained by an attacker, the leaked session identifier could potentially be used for session hijacking.\n\nAdditionally, the implementation did not regenerate the session identifier after successful authentication, leaving authenticated sessions susceptible to session fixation attacks where an attacker forces a victim to use a known session identifier before login and later reuses that identifier after authentication.\n\nThe OAuth state value was also not implemented as a dedicated, single-use nonce. This weakened CSRF protections and increased the risk of replay attacks against the OAuth callback process.\n\nThe authentication flow further failed to enforce HTTPS for the configured OAuth redirect URI. If a non-HTTPS redirect URI was used, OAuth authorization codes and access tokens could traverse the network in plaintext, exposing sensitive credentials to network attackers.\n\nFinally, OAuth error responses containing attacker-controlled GET parameters were logged verbatim. An attacker could inject control characters or crafted log content, leading to log forging, log injection, or corruption of audit records.\n\nThe fix introduces:\n\n  *  \nA dedicated cryptographically random OAuth state value.\n\n  *  \nSingle-use state validation and invalidation.\n\n  *  \nConstant-time state comparison using hash_equals().\n\n  *  \nSession identifier rotation after successful authentication.\n\n  *  \nEnforcement of HTTPS-only redirect URIs.\n\n  *  \nSanitized and length-limited logging of OAuth error parameters.\n\nAAD Authentication Plugin (OAuth 2.0 / Azure Active Directory integration)","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":"Auth bypass in misp","id":"CVE-2026-56425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"misp-project:misp","products":["misp-project:misp"],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in BSH ELP (Electronic Platform) Modules","id":"CVE-2026-56428"},"packages":[],"prev":{"headline":"Missing authorization in misp","id":"CVE-2026-56424"},"products":["misp"],"published":"2026-06-22","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-46918","kev_date_added":null,"published":"2024-09-15"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-45509","kev_date_added":null,"published":"2024-09-01"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-29858","kev_date_added":null,"published":"2024-03-21"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-29859","kev_date_added":null,"published":"2024-03-21"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-25674","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-25675","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-50918","kev_date_added":null,"published":"2023-12-15"}],"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":"total"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["misp"]},"summary":"Attackers can hijack sessions or bypass OAuth security via weak state handling and missing session rotation in the MISP AAD authentication plugin.","url":"https://insights.sbomify.com/CVE-2026-56425/"}