{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-55676 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-55676 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55676 is a high-severity vulnerability in cisagov Malcolm, published on 11 Aug 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-55676 and fix it if it is affected.\n\nWhat it is: CVE-2026-55676 is a high-severity vulnerability in cisagov Malcolm, published on 11 Aug 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-55676 in the wild and no public exploit code.\n\nAffected product: cisagov Malcolm. 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-55676/ (Markdown: https://insights.sbomify.com/CVE-2026-55676/index.md)","id":"CVE-2026-55676","markdown":"https://insights.sbomify.com/CVE-2026-55676/index.md","name":"CVE-2026-55676","record":{"aliases":["GHSA-8cvp-m7pg-qrp7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Network traffic analysis tool","requires_auth":"low_privilege","summary":"An attacker with upload privileges can execute arbitrary PHP code by uploading a malicious file due to missing file type restrictions.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","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-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Malcolm is a network traffic analysis tool suite. The file-upload component (FilePond PHP backend) accepts uploads at `POST /server/php/submit.php` and stores them in a directory served by the same nginx and php-fpm instance. The allow-list that should restrict accepted file types is an empty array by default (`file-upload/php/config.php:16`), so the type check is a no-op and every extension is accepted. The filename sanitizer keeps the `.php` extension intact. Committed files land in `/var/www/upload/server/php/files` (`file-upload/php/config.php:7`), and the component's nginx routes any URL ending in `.php` to php-fpm. An authenticated `GET /server/php/files/\u003cname\u003e.php` then executes the uploaded code as `www-data`. Prior to version 26.06.1, in RBAC mode, the upload endpoint is reachable by the granular `ROLE_UPLOAD` role (`nginx/lua/nginx_auth_helpers.lua:71`), a role intended only for submitting capture files. As a result, a user holding the upload-only role runs arbitrary PHP as `www-data` inside the file-upload container. Version 26.06.1 fixes the issue.","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":"Malcolm vulnerable to RCE via unrestricted .php upload to the file-upload component","id":"CVE-2026-55676","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files","id":"CVE-2026-55677"},"packages":[],"prev":{"headline":"Salty documentation workflow executes fork-controlled Python build hooks with deployment secrets","id":"CVE-2026-55675"},"products":["Malcolm"],"published":"2026-08-11","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-10-02","vendors":["cisagov"]},"summary":"An attacker with upload privileges can execute arbitrary PHP code by uploading a malicious file due to missing file type restrictions.","url":"https://insights.sbomify.com/CVE-2026-55676/"}