[GHSA-jc85-fpwf-qm7x] expr-eval does not restrict functions passed to the evaluate function #6479
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates
Comments
Mitigation Solution: safe-expr-eval
I've developed safe-expr-eval as a secure drop-in replacement that completely addresses CVE-2025-12735 while maintaining 100% API compatibility with expr-eval.
Why safe-expr-eval is secure:
✅ No eval() - Never uses JavaScript's dangerous eval() function
✅ No Function constructor - Doesn't dynamically create executable code
✅ Token-based parsing - Expressions are parsed into safe tokens and evaluated in a controlled environment
✅ Type-safe - Built with TypeScript for additional security guarantees
✅ Zero dependencies - Minimal attack surface
Migration is trivial: