GHSA-M2PC-3Q4Q-W6JR

Vulnerability from github – Published: 2026-08-25 17:38 – Updated: 2026-08-25 17:38
VLAI
Summary
reachy_mini Allows Unrestricted Upload of File with Dangerous Type
Details

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:

  1. Unrestricted File Upload in Media Sounds Upload API \<= current finding
  2. Bluetooth Authentication Bypass
  3. 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/<original_filename>``.
    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 = os.path.join(SOUNDS_TMP_DIR, filename)
    content = await file.read()
    with open(dest, "wb") as f:
        f.write(content)
    return {"status": "ok", "path": dest}

This endpoint lacks multiple defence mechanisms:

  1. No authentication mechanism.
  2. No file extension validation.
  3. No file content/size validation.

Additionally, 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.

PoC

  1. Start the daemon in simulation mode (command depends on the installed environment):
 .venv/bin/mjpython -m reachy_mini.daemon.app.main --sim --no-media
  1. After that check that the media upload API endpoint is activated and you can upload a wav file:
curl -X POST http://<daemon_domain>:<daemon_port>/api/media/sounds/upload \
    -F "file=@/path/to/your/file.wav"
  1. Now attempt to create a “.sh” file containing a script and upload it:
curl -X POST http://<daemon_domain>:<daemon_port>/api/media/sounds/upload \
    -F "file=@/path/to/your/script.sh"
  1. Now error message will be received and you will see that the script file was successfully uploaded to disk.

Impact

Due 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.

Fix suggestion

Perform the following check on the API endpoint:

  1. Validate that the file extension contains only desired extensions (allow-list approach).
  2. Validate that the uploaded file’s content matches the desired extension (Magic numbers, and known file structure per file type).
  3. Enforce authentication on the file upload endpoint.

Credit

The vulnerability was discovered by Natan Nehorai of the JFrog Vulnerability Research team.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "reachy-mini"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.8.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-55419"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-434"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-08-25T17:38:43Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "## Summary\n\nThe Reachy Mini daemon exposes the \u201c/api/media/sounds/upload\u201d 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\u2019s operating system:\n\n1. Unrestricted File Upload in Media Sounds Upload API \\\u003c= 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 \u201c***src/daemon/app/routers/media.py***\u201d file at the \u201cupload\\_sound\u201d method:\n\n```py\n@router.post(\"/sounds/upload\")\nasync def upload_sound(\n    file: UploadFile = File(...),\n) -\u003e dict[str, str]:\n    \"\"\"Upload a sound file to the daemon\u0027s temporary sound directory.\n    The file is saved to ``/tmp/reachy_mini_sounds/\u003coriginal_filename\u003e``.\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=\\[\u201c\\*\u201d\\] ) 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://\u003cdaemon_domain\u003e:\u003cdaemon_port\u003e/api/media/sounds/upload \\\n    -F \"file=@/path/to/your/file.wav\"\n```\n\n3. Now attempt to create a \u201c.sh\u201d file containing a script and upload it:\n\n```shell\ncurl -X POST http://\u003cdaemon_domain\u003e:\u003cdaemon_port\u003e/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\u2019s 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.",
  "id": "GHSA-m2pc-3q4q-w6jr",
  "modified": "2026-08-25T17:38:43Z",
  "published": "2026-08-25T17:38:43Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "reachy_mini Allows Unrestricted Upload of File with Dangerous Type"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…