Arbitrary code execution via untrusted context functions
Published Nov 5, 2025 · Updated Nov 5, 2025
Code injection in expr-eval through 2.0.2 and expr-eval-fork through 3.0.0 allows attackers to execute code via crafted evaluator input. The evaluate() path accepts callable values from its context object and invokes them without requiring registration on the parser's function allowlist. Attackers must control an expression and its context values processed by the host application; successful exploitation runs with that process's privileges.
Summary
What happened
Code injection in expr-eval through 2.0.2 and expr-eval-fork through 3.0.0 allows attackers to execute code via crafted evaluator input. The evaluate() path accepts callable values from its context object and invokes them without requiring registration on the parser's function allowlist. Attackers must control an expression and its context values processed by the host application; successful exploitation runs with that process's privileges.
The record
- CVE
- CVE-2025-12735
- Published
- Nov 5, 2025
- Updated
- Nov 5, 2025
- Vendor
- jorenbroekema
- Product
- expr-eval-fork
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 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.2
What conditions does exploitation require?
What is affected?
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
- CERT/CC researcher proof-of-concept security testproof 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