CVE-2026-55419

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 26, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.8.2

Patch available: pollen-robotics/reachy_mini v1.8.2

https://github.com/pollen-robotics/reachy_mini/releases/tag/v1.8.2
github_commit Patch Available

commit 984c7723b3ec (pollen-robotics/reachy_mini)

Patch available: pollen-robotics/reachy_mini v1.8.2 (contains commit 984c7723b3ec)

https://github.com/pollen-robotics/reachy_mini/commit/984c7723b3ec5da63f4e0a2bcf9f120ceb563e04
github_pr Patch Available

Fix media sounds upload validation

Patch available: pollen-robotics/reachy_mini v1.8.2 (PR #1209 merged 2026-06-15)

https://github.com/pollen-robotics/reachy_mini/pull/1209
github Patch Available🟡 PoC Available

Unrestricted Upload of File with Dangerous Type in reachy_mini · Advisory · pollen-robotics/reachy_mini · GitHub

https://github.com/pollen-robotics/reachy_mini/security/advisories/GHSA-m2pc-3q4q-w6jr

Vendor Advisories for CVE-2026-55419(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
reachy-mini1.0.0 ... 1.8.1 (58 versions)1.8.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-29 00:52 UTCEG score recompute
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-27 22:44 UTCEG score recompute
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 20:41 UTCEG score recompute
  6. 2026-08-26 19:30 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 18:27 UTCEG score recompute
  9. 2026-08-25 17:40 UTCEG score recompute
  10. 2026-08-25 17:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55419?
CVE-2026-55419 is a medium vulnerability published on August 25, 2026. 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 uploadsound method in src/reachymini/daemon/app/routers/media.py without authentication, file-extension checks, content validation, or…
When was CVE-2026-55419 disclosed?
CVE-2026-55419 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55419 actively exploited?
CVE-2026-55419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-55419?
CVE-2026-55419 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-55419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55419, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55419

Explore →

Is Your Infrastructure Affected by CVE-2026-55419?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.