Skip to main content
CVE-2024-39934VulnerabilityPublished Updated

CVE-2024-39934: robotmk · n/a

Affects robotmkSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High : upgrade to 2.0.1 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.1
CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade elabit/robotmk to 2.0.1.

Affected software

ProductAffectedFixed in
GitHubelabit/robotmkpkg:github/elabit/robotmkOther threatsAffected
  • <2.0.1
Fixed in
  • 2.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-39934, organizations should immediately upgrade Robotmk to version 2.0.1 or later, where this vulnerability is addressed. If upgrading is not immediately feasible, disable the automated Python environment setup feature or the 'shared holotree usage' functionality to prevent unauthorized modifications. Implement strict access controls and limit local user permissions to reduce the risk of exploitation. Regularly audit and monitor Python environment directories for unauthorized changes. Employ endpoint detection and response (EDR) solutions to detect suspicious local privilege escalation attempts. Additionally, enforce the principle of least privilege for all users and restrict local access to trusted personnel only. Maintain up-to-date backups and have an incident response plan ready to address potential compromises stemming from privilege escalation attacks.

Description

Robotmk before 2.0.1 allows a local user to escalate privileges (e.g., to SYSTEM) if automated Python environment setup is enabled, because the "shared holotree usage" feature allows any user to edit any Python environment.

References

Community reviews

Loading reviews…