Dexbotic CVE-2026-117510

Exploitation requires the victim to load an attacker-influenced pretrained checkpoint through the gr00tsonic Checkpoint Loader, specifically where the weight_map argument of load_pretrained_gr00t is attacker-controlled; the traversal is triggered during that checkpoint-loading operation. Per the CVSS vector no authentication is needed (PR:N), but passive user interaction is required (UI:P) - a user or automated pipeline must actually load the untrusted checkpoint, which is the primary limiting factor. Risk is further bounded to deployments running Dexbotic 0.1 or 0.2.0 that ingest checkpoints from untrusted sources; environments that only load self-produced checkpoints are not realistically exposed. No special network service or non-default feature flag is described beyond use of the checkpoint loader itself.

All available signals point to a genuinely low-priority issue rather than a high-CVSS-but-overrated one. The supplied CVSS 4.0 base score is only 2.1, and its metrics are internally consistent with a minor flaw: network vector (AV:N) and low complexity (AC:L) with no privileges (PR:N) but passive user interaction required (UI:P), and only Low impact to confidentiality, integrity and availability (VC:L/VI:L/VA:L) with no subsequent-system scope change (SC:N/SI:N/SA:N). There is no EPSS score in the input and no CISA KEV listing, so there is no evidence of widespread or active exploitation. The vuln.today decision label is 'monitor', the weakest urgency tier, which agrees with the low score. A public PoC reference (a poc.zip attachment) exists but is explicitly not verified as working exploit code, so it should not be treated as confirmed weaponization. The main tension is between the description's phrase 'Remote exploitation of the attack is possible' and the UI:P metric: exploitation is remote in the sense that an attacker-supplied checkpoint/weight_map can be delivered over the network, but the victim must load that untrusted checkpoint, which materially limits real-world risk. Reporting is solely third-party (VulDB); there is no vendor advisory, the project was notified but has not responded, and no fixed version is listed - verify affected scope and any fix directly with the Dexbotic project.

An attacker publishes or supplies a malicious model checkpoint whose weight_map argument contains path-traversal sequences; when a developer or operator loads it through load_pretrained_gr00t in Dexbotic's gr00tsonic Checkpoint Loader, the traversal causes file access outside the intended checkpoint directory. A public PoC reference (poc.zip) is attached but is not verified as working exploit code. Exploitation hinges on the victim choosing to load the untrusted checkpoint (UI:P), so it is opportunistic rather than fully automatic.