CVE-2025-62162
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedcel-rust is a Common Expression Language interpreter written in Rust. Starting in version 0.10.0 and prior to version 0.11.4, parsing certain malformed CEL expressions can cause the parser to panic, terminating the process. When the crate is used to evaluate untrusted expressions (e.g., user-supplied input over an API), an attacker can send crafted input to trigger a denial of service (DoS). Version 0.11.4 fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe cel-rust library (Common Expression Language interpreter in Rust) has a denial-of-service vulnerability where parsing malformed CEL expressions triggers a parser panic, causing process termination. Attackers can exploit this by supplying crafted malicious input to APIs that evaluate user-supplied CEL expressions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify cel-rust library versionSearch your dependency files (Cargo.toml, Cargo.lock) or installed package listings for the cel-rust or cel-parser crate and note its version numberAffected if The installed version is lower than 0.11.4 (e.g., 0.11.3, 0.11.2, etc.)
-
Locate CEL expression evaluation codeSearch your codebase for imports of cel-rust crates and calls to expression evaluation functions such as cel::evaluate, parser::parse, or similar CEL evaluation APIsAffected if Your application calls CEL evaluation functions on user-supplied input without sanitization
-
Identify user-facing endpointsReview your API endpoints or functions that accept CEL expressions from external sources (HTTP requests, CLI arguments, database fields, message queues)Affected if Untrusted users or external systems can submit CEL expressions to your service
-
Check for input validationExamine the CEL evaluation code path for validation logic that filters or rejects malformed expressions before parsingAffected if No input validation exists on CEL expression input before it reaches the parser
-
Verify rate limiting or throttlingCheck if rate limiting, timeouts, or resource constraints are applied to endpoints that process CEL expressionsAffected if No rate limiting or execution timeout is configured for CEL expression evaluation
You are affected if your environment runs cel-rust version below 0.11.4 AND accepts CEL expressions from untrusted sources without input validation or rate limiting.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade cel-rust to version 0.11.4 or later. If upgrade is not immediately possible, implement input validation and rate limiting on endpoints that evaluate CEL expressions to reduce DoS exposure.
0.11.4
- Update the cel-rust dependency in your Cargo.toml to version 0.11.4 or later
- Run `cargo update` or `cargo upgrade cel-runtime` to fetch the fixed version
- Rebuild and test your application to ensure the update doesn't break existing functionality
- Redeploy your service with the updated dependency
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62162 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data