Local code execution via unverified compiled instructions
Published May 2, 2025 · Updated May 5, 2025
Code injection in handrew BrowserPilot 0.2.0 through 0.2.51 allows local users to execute Python code through crafted instructions. The __run_compiled_instructions method passes InstructionCompiler output directly to exec() with global and local namespaces, without verification. A local low-privileged user who controls compiler input can run code with the BrowserPilot process's permissions, enabling file access or modification.
Summary
What happened
Code injection in handrew BrowserPilot 0.2.0 through 0.2.51 allows local users to execute Python code through crafted instructions. The __run_compiled_instructions method passes InstructionCompiler output directly to exec() with global and local namespaces, without verification. A local low-privileged user who controls compiler input can run code with the BrowserPilot process's permissions, enabling file access or modification.
The record
- CVE
- CVE-2025-4218
- Published
- May 2, 2025
- Updated
- May 5, 2025
- Vendor
- handrew
- Product
- BrowserPilot
- Classifications
- CWE-74, CWE-94, T1059.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0
- Affected versionversion=0.2.1
- Affected versionversion=0.2.10
- Affected versionversion=0.2.11
- Affected versionversion=0.2.12
- Affected versionversion=0.2.13
- Affected versionversion=0.2.14
- Affected versionversion=0.2.15
- Affected versionversion=0.2.16
- Affected versionversion=0.2.17
- Affected versionversion=0.2.18
- Affected versionversion=0.2.19
- Affected versionversion=0.2.2
- Affected versionversion=0.2.20
- Affected versionversion=0.2.21
- Affected versionversion=0.2.22
- Affected versionversion=0.2.23
- Affected versionversion=0.2.24
- Affected versionversion=0.2.25
- Affected versionversion=0.2.26
- Affected versionversion=0.2.27
- Affected versionversion=0.2.28
- Affected versionversion=0.2.29
- Affected versionversion=0.2.3
- Affected versionversion=0.2.30
- Affected versionversion=0.2.31
- Affected versionversion=0.2.32
- Affected versionversion=0.2.33
- Affected versionversion=0.2.34
- Affected versionversion=0.2.35
- Affected versionversion=0.2.36
- Affected versionversion=0.2.37
- Affected versionversion=0.2.38
- Affected versionversion=0.2.39
- Affected versionversion=0.2.4
- Affected versionversion=0.2.40
- Affected versionversion=0.2.41
- Affected versionversion=0.2.42
- Affected versionversion=0.2.43
- Affected versionversion=0.2.44
- Affected versionversion=0.2.45
- Affected versionversion=0.2.46
- Affected versionversion=0.2.47
- Affected versionversion=0.2.48
- Affected versionversion=0.2.49
- Affected versionversion=0.2.5
- Affected versionversion=0.2.50
- Affected versionversion=0.2.51
- Affected versionversion=0.2.6
- Affected versionversion=0.2.7
- Affected versionversion=0.2.8
- Affected versionversion=0.2.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- BrowserPilot Issue 20 exploit procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo