Improper Validation of Unsafe Equivalence in Input Affecting cel package, versions >=0.10.0 <0.11.4
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RUST-CEL-13535099
- published12 Oct 2025
- disclosed10 Oct 2025
- creditJohn Howard
Introduced: 10 Oct 2025
NewCVE-2025-62162 (opens in a new tab)How to fix?
Upgrade cel to version 0.11.4 or higher.
Overview
cel is a non-Turing complete language designed for simplicity, speed, safety, and portability. CEL's C-like syntax looks nearly identical to equivalent expressions in C++, Go, Java, and TypeScript. CEL is ideal for lightweight expression evaluation when a fully sandboxed scripting language is too resource intensive.
Affected versions of this package are vulnerable to Improper Validation of Unsafe Equivalence in Input via the parser implementation. An attacker can cause the application to terminate unexpectedly by submitting specially crafted malformed expressions.
PoC
use cel::{Context, Program};
fn main() {
let program = Program::compile("x(1,").unwrap();
let context = Context::default();
let value = program.execute(&context).unwrap();
assert_eq!(value, true.into());
}