CVE-2026-55419: Reachy mini Reachy_mini Allows Unrestricted Upload Of Vulnerability
MODERATECVE-2026-55419 is a MODERATE (CVSS 5.3) reachy_mini allows unrestricted upload of vulnerability (CWE-434: Unrestricted Upload of File with Dangerous Type) affecting Reachy mini libraries in the PyPI ecosystem. The issue involves reachy_mini allows unrestricted upload of file with dangerous type. Remediation is available by upgrading affected packages to version 1.8.2.
CVE-2026-55419 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).
How to Fix CVE-2026-55419
To remediate this vulnerability, upgrade all affected Reachy mini dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install reachy-mini>=1.8.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show reachy-mini
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-55419, inspect your installed packages using pip:
pip show reachy-mini
Analyze the terminal output to locate any version of Reachy mini in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.8.2), your application is affected.
Note: The pip show reachy-mini command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-434: Unrestricted Upload of File with Dangerous Type, where the product allows the upload or transfer of dangerous file types that are automatically processed within its environment. In Reachy mini, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-55419 Affected Reachy mini Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
reachy-mini
|
PyPI |
< 1.8.2
|
1.8.2
|
References
Frequently Asked Questions
What is CVE-2026-55419?
Which Reachy mini versions are affected?
What version fixes CVE-2026-55419?
Is reachy-mini affected?
What is the CVSS score of CVE-2026-55419?
What CWE is associated with CVE-2026-55419?
How can I check PyPI dependencies for CVE-2026-55419?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m2pc-3q4q-w6jr",
"modified" : "2026-08-25T17:38:43Z",
"published" : "2026-08-25T17:38:43Z",
"aliases" : [ "CVE-2026-55419" ],
"summary" : "reachy_mini Allows Unrestricted Upload of File with Dangerous Type",
"details" : "## Summary\n\nThe Reachy Mini daemon exposes the “/api/media/sounds/upload” endpoint without authentication and file validation mechanisms. \nAn attacker can use this endpoint to upload malicious files into the file system that will propagate in future attacks.\n\n## Compromise Chain: Unauthenticated to Full Root Access\n\nThis issue is part of a full compromise chain allowing an unauthenticated user to gain root access on the Reachy’s operating system:\n\n1. Unrestricted File Upload in Media Sounds Upload API \\<= current finding \n2. Bluetooth Authentication Bypass \n3. Bluetooth Directory Traversal\n\n\n## Description\n\nThe root cause of the issue is at the handler located in “***src/daemon/app/routers/media.py***” file at the “upload\\_sound” method:\n\n```py\n@router.post(\"/sounds/upload\")\nasync def upload_sound(\n file: UploadFile = File(...),\n) -> dict[str, str]:\n \"\"\"Upload a sound file to the daemon's temporary sound directory.\n The file is saved to ``/tmp/reachy_mini_sounds/<original_filename>``.\n If a file with the same name already exists it is overwritten.\n Returns:\n JSON with the absolute *path* of the saved file on the daemon.\n \"\"\"\n if not file.filename:\n raise HTTPException(status_code=400, detail=\"Filename is required\")\n # Reject path traversal\n filename = Path(file.filename).name\n if not filename or filename in (\".\", \"..\"):\n raise HTTPException(status_code=400, detail=\"Invalid filename\")\n os.makedirs(SOUNDS_TMP_DIR, exist_ok=True)\n dest = os.path.join(SOUNDS_TMP_DIR, filename)\n content = await file.read()\n with open(dest, \"wb\") as f:\n f.write(content)\n return {\"status\": \"ok\", \"path\": dest}\n```\n\nThis endpoint lacks multiple defence mechanisms:\n\n1. No authentication mechanism. \n2. No file extension validation. \n3. No file content/size validation.\n\nAdditionally, the daemon is bound to the 0.0.0.0 network interfaces (a.k.a. all network interfaces) by default along with permissive CORS ( allow\\_origins=\\[“\\*”\\] ) meaning the following API endpoint is exposed to every network interface the daemon is connected to.\n\n# PoC\n\n1. Start the daemon in simulation mode (command depends on the installed environment):\n\n```shell\n .venv/bin/mjpython -m reachy_mini.daemon.app.main --sim --no-media\n```\n\n2. After that check that the media upload API endpoint is activated and you can upload a wav file:\n\n```shell\ncurl -X POST http://<daemon_domain>:<daemon_port>/api/media/sounds/upload \\\n -F \"file=@/path/to/your/file.wav\"\n```\n\n3. Now attempt to create a “.sh” file containing a script and upload it:\n\n```shell\ncurl -X POST http://<daemon_domain>:<daemon_port>/api/media/sounds/upload \\\n -F \"file=@/path/to/your/script.sh\"\n```\n\n4. Now error message will be received and you will see that the script file was successfully uploaded to disk.\n\n# Impact\n\nDue to this issue, an attacker can upload malicious files instead of the intended sounds files, harming the integrity of the stored data and allowing an attacker to propagate a foothold in cases another vulnerabilities would arise.\n\n## Fix suggestion\n\nPerform the following check on the API endpoint:\n\n1. Validate that the file extension contains only desired extensions (allow-list approach). \n2. Validate that the uploaded file’s content matches the desired extension (Magic numbers, and known file structure per file type). \n3. Enforce authentication on the file upload endpoint.\n\n## Credit\n\nThe vulnerability was discovered by Natan Nehorai of the JFrog Vulnerability Research team.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "reachy-mini"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.8.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/pollen-robotics/reachy_mini/security/advisories/GHSA-m2pc-3q4q-w6jr"
}, {
"type" : "WEB",
"url" : "https://github.com/pollen-robotics/reachy_mini/commit/984c7723b3ec5da63f4e0a2bcf9f120ceb563e04"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/pollen-robotics/reachy_mini"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-434" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-25T17:38:43Z",
"nvd_published_at" : null
}
}