{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-56446 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56446 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56446 is a high-severity code injection vulnerability in Misp-Project Misp, published on 22 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56446 and fix it if it is affected.\n\nWhat it is: CVE-2026-56446 is a high-severity code injection vulnerability in Misp-Project Misp, published on 22 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56446 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-56446/ (Markdown: https://insights.sbomify.com/CVE-2026-56446/index.md)","id":"CVE-2026-56446","markdown":"https://insights.sbomify.com/CVE-2026-56446/index.md","name":"CVE-2026-56446","record":{"aliases":["GHSA-7v9f-64q7-x2jg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MISP threat sharing","requires_auth":"high_privilege","summary":"Authenticated site administrators can achieve remote code execution by configuring the NDJSON error log to a web-accessible PHP file and injecting code via log entries.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[{"product":"misp","vendor":"misp-project"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"MISP allowed a site administrator to configure an arbitrary filesystem path for the NDJSON error log used by JsonLogTool. Because log entries can include attacker-controlled content, an authenticated attacker with site administrator privileges could direct log output to a PHP file in a web-accessible directory and inject PHP code through logged data. Accessing the resulting file could lead to remote code execution with the privileges of the web server process.\n\nThe fix restricts log destinations to existing directories beneath APP/tmp/logs or /var/log, requires absolute paths, rejects stream wrappers and traversal-related input, and limits filenames to .log or .ndjson extensions while disallowing executable extension segments.","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":"Authenticated Remote Code Execution via Arbitrary NDJSON Error Log Path in MISP","id":"CVE-2026-56446","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"misp-project:misp","products":["misp-project:misp"],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MISP remote code execution via arbitrary rdkafka configuration path","id":"CVE-2026-56447"},"packages":[],"prev":{"headline":"pydicom pynetdicom Library Path Traversal","id":"CVE-2026-56445"},"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":"Authenticated site administrators can achieve remote code execution by configuring the NDJSON error log to a web-accessible PHP file and injecting code via log entries.","url":"https://insights.sbomify.com/CVE-2026-56446/"}