Unrestricted File Upload in reachy-mini (CVE-2026-55419)
Summary
Vulnerability in reachy-mini (CVE-2026-55419). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.8.2 or later.
Original description
The description as published by the source.
Summary
The Reachy Mini daemon exposes the “/api/media/sounds/upload” endpoint without authentication and file validation mechanisms.
An attacker can use this endpoint to upload malicious files into the file system that will propagate in future attacks.
Compromise Chain: Unauthenticated to Full Root Access
This issue is part of a full compromise chain allowing an unauthenticated user to gain root access on the Reachy’s operating system:
- Unrestricted File Upload in Media Sounds Upload API <= current finding
- Bluetooth Authentication Bypass
- Bluetooth Directory Traversal
Description
The root cause of the issue is at the handler located in “src/daemon/app/routers/media.py” file at the “upload_sound” method:
@router.post("/sounds/upload")
async def upload_sound(
file: UploadFile = File(...),
) -> dict[str, str]:
"""Upload a sound file to the daemon's temporary sound directory.
The file is saved to ``/tmp/reachy_mini_sounds/``.
If a file with the same name already exists it is overwritten.
Returns:
JSON with the absolute *path* of the saved file on the daemon.
"""
if not file.filename:
raise HTTPException(status_code=400, detail="Filename is required")
# Reject path traversal
filename = Path(file.filename).name
if not filename or filename in (".", ".."):
raise HTTPException(status_code=400, detail="Invalid filename")
os.makedirs(SOUNDS_TMP_DIR, exist_ok=True)
dest = o…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55419 has been found in reachy-mini.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade reachy-mini to 1.8.2 or later.
If unsure, ask your IT team or search "reachy-mini CVE-2026-55419" on the vendor's site.
CVE-2026-55419 (reachy-mini) — CWE-434 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.8.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-434) exists in reachy-mini.
Check the vendor advisory for the affected versions of reachy-mini.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.8.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'reachy-mini' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'reachy-mini' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
reachy-miniを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade reachy-mini to 1.8.2ステージング環境で 1.8.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。