{"answers":{"affected":"3 open source packages ship an affected version, including reachy-mini.","exploited":"There is no known exploitation of CVE-2026-55419 in the wild and no public exploit code.","fix":"Upgrade reachy-mini to 1.8.2 or later.","what":"CVE-2026-55419 is a medium-severity vulnerability in pollen-robotics reachy_mini, published on 25 Aug 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-55419 and fix it if it is affected.\n\nWhat it is: CVE-2026-55419 is a medium-severity vulnerability in pollen-robotics reachy_mini, published on 25 Aug 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-55419 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- reachy-mini (PyPI): affected all versions; fixed in 1.8.2\n- reachy-mini (PyPI): affected all versions; fixed in 1.8.2\n- reachy-mini (PyPI): affected all versions; fixed in 1.8.2\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-55419/ (Markdown: https://insights.sbomify.com/CVE-2026-55419/index.md)","id":"CVE-2026-55419","markdown":"https://insights.sbomify.com/CVE-2026-55419/index.md","name":"CVE-2026-55419","record":{"aliases":["GHSA-m2pc-3q4q-w6jr","PYSEC-2026-3916"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Robot control SDK","requires_auth":"none","summary":"Unauthenticated attackers can upload arbitrary files to Reachy Mini robots, compromising data integrity and potentially enabling code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Reachy Mini is an SDK for controlling Reachy Mini robots. Prior to 1.8.2, the Reachy Mini daemon exposes the /api/media/sounds/upload endpoint implemented by the upload_sound method in src/reachy_mini/daemon/app/routers/media.py without authentication, file-extension checks, content validation, or size validation. The daemon binds to 0.0.0.0 by default and uses permissive CORS allow_origins=[\"*\"], allowing an unauthenticated network attacker to upload arbitrary file types that are written to /tmp/reachy_mini_sounds/\u003coriginal_filename\u003e. Malicious files can compromise stored-data integrity and can serve as a foothold when combined with other vulnerabilities. This issue is fixed in version 1.8.2.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Reachy Mini: Unrestricted Upload of File with Dangerous Type","id":"CVE-2026-55419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Discourse: Remote code execution via pdf uploads","id":"CVE-2026-55420"},"packages":[{"ecosystem":"PyPI","fixed":["1.8.2"],"introduced":["0"],"last_affected":[],"package":"reachy-mini","purl":null,"source":"GHSA-m2pc-3q4q-w6jr"},{"ecosystem":"PyPI","fixed":["1.8.2"],"introduced":["0"],"last_affected":[],"package":"reachy-mini","purl":"pkg:pypi/reachy-mini","source":"GHSA-m2pc-3q4q-w6jr"},{"ecosystem":"PyPI","fixed":["1.8.2"],"introduced":["0"],"last_affected":[],"package":"reachy-mini","purl":"pkg:pypi/reachy-mini","source":"PYSEC-2026-3916"}],"prev":{"headline":"FastGPT: S3 presign/read handlers do not bind the object key to the caller's team (cross-team file disclosure)","id":"CVE-2026-55418"},"products":["reachy_mini"],"published":"2026-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-08-26","vendors":["pollen-robotics"]},"summary":"Unauthenticated attackers can upload arbitrary files to Reachy Mini robots, compromising data integrity and potentially enabling code execution.","url":"https://insights.sbomify.com/CVE-2026-55419/"}