chore(deps): update module github.com/expr-lang/expr to v1.17.7 [security]

[renovate-sh-app]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/expr-lang/expr	v1.17.6 → v1.17.7

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2025-68156

Several builtin functions in Expr, including flatten, min, max, mean, and median, perform
recursive traversal over user-provided data structures without enforcing a maximum recursion depth.

If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse
indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host
application to crash.

While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness.
Instead of returning a recoverable evaluation error, the process may terminate unexpectedly.

Impact

In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently
validated data structures can lead to a process-level crash due to stack exhaustion.

This issue is most relevant in scenarios where:

• Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.
• Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.
• There are no application-level safeguards preventing deeply nested input data.

In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting
panic can be used to reliably crash the application, constituting a denial of service.

Patches

The issue has been fixed in the v1.17.7 versions of Expr.

The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded,
evaluation aborts gracefully and returns a descriptive error instead of panicking.

Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate
deep structures to raise the limit in a controlled manner.

Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and
comprehensive test coverage to prevent regressions.

Workarounds

For users who cannot immediately upgrade, the following mitigations are recommended:

• Ensure that evaluation environments cannot contain cyclic references.
• Validate or sanitize externally supplied data structures before passing them to Expr.
• Wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure).

These workarounds reduce risk but do not fully eliminate the issue without the patch.

---

Expr has Denial of Service via Unbounded Recursion in Builtin Functions

CVE-2025-68156 / GHSA-cfpf-hrx2-8rv6 / GO-2025-4245

More information

Details

Several builtin functions in Expr, including flatten, min, max, mean, and median, perform
recursive traversal over user-provided data structures without enforcing a maximum recursion depth.

If the evaluation environment contains deeply nested or cyclic data structures, these functions may recurse
indefinitely until exceed the Go runtime stack limit. This results in a stack overflow panic, causing the host
application to crash.

While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness.
Instead of returning a recoverable evaluation error, the process may terminate unexpectedly.

Impact

In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently
validated data structures can lead to a process-level crash due to stack exhaustion.

This issue is most relevant in scenarios where:

• Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.
• Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.
• There are no application-level safeguards preventing deeply nested input data.

In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting
panic can be used to reliably crash the application, constituting a denial of service.

Patches

The issue has been fixed in the v1.17.7 versions of Expr.

The patch introduces a maximum recursion depth limit for affected builtin functions. When this limit is exceeded,
evaluation aborts gracefully and returns a descriptive error instead of panicking.

Additionally, the maximum depth can be customized by users via builtin.MaxDepth, allowing applications with legitimate
deep structures to raise the limit in a controlled manner.

Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and
comprehensive test coverage to prevent regressions.

Workarounds

For users who cannot immediately upgrade, the following mitigations are recommended:

• Ensure that evaluation environments cannot contain cyclic references.
• Validate or sanitize externally supplied data structures before passing them to Expr.
• Wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure).

These workarounds reduce risk but do not fully eliminate the issue without the patch.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/expr-lang/expr/security/advisories/GHSA-cfpf-hrx2-8rv6
• https://nvd.nist.gov/vuln/detail/CVE-2025-68156
• https://github.com/expr-lang/expr/pull/870
• https://github.com/expr-lang/expr

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Expr has Denial of Service via Unbounded Recursion in Builtin Functions in github.com/expr-lang/expr

CVE-2025-68156 / GHSA-cfpf-hrx2-8rv6 / GO-2025-4245

More information

Details

Expr has Denial of Service via Unbounded Recursion in Builtin Functions in github.com/expr-lang/expr

Severity

Unknown

References

• https://github.com/expr-lang/expr/security/advisories/GHSA-cfpf-hrx2-8rv6
• https://github.com/expr-lang/expr/pull/870

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).

---

Release Notes

expr-lang/expr (github.com/expr-lang/expr)

v1.17.7

Compare Source

Expr is a Go-centric expression language designed to deliver dynamic configurations with unparalleled accuracy,
safety, and speed.

program, err := expr.Compile(`let foo = bar(); baz(foo, foo)`)

This release brings new language features, performance improvements across runtime and compiler, better error
handling, and many important bug fixes.

New Features

Support for else if expressions

• You can now chain conditional branches using else if! (#​879)

Unicode escapes in the \u{XXXXXX} format

• String literals now support Unicode code point escapes such as \u{1F600}. (#​882)

Byte slice support in the matches operator

The matches operator now works with []byte, improving interoperability with binary data. (#​876)

Short-circuit control options

New options allow enabling or disabling short-circuiting behavior in the compiler and VM. (#​847)

Option to disable if operator

A separate DisableIfOperator option is now available. (#​881)

Performance Improvements

Runtime structure fetch improvements

Accessing struct fields at runtime is now faster. (#​833)

VM function call optimizations

Function calls inside the VM execute more efficiently. (#​832)

Type system performance boost

Large or complex type operations now run significantly faster. (#​824)

Bug Fixes

• Guard negative forward jump offsets (#​861).
• Prevent stack underflow in the VM (#​860).
• Correct behavior of AsBool with nil and undefined variables (#​866).
• Proper handling of nil arguments in variadic functions (#​868).
• Show function name for safe calls in disassembly (#​869).
• Limit recursion depth in built-in functions (#​870).
• Throw an error when a predicate is missing in the parser (#​842).
• Fixed array type resolution in conditional operator (#​865).
• Disallow access to unexported struct fields (#​846).
• Fixed retrieving field pointers in structs (#​843).
• Better error position reporting in multi-line scripts (#​827).
• Support quoting backticks inside string literals (#​820).
• Fixed auto-dereference for maps/slices and conditionals (#​871).
• Wrap merged optimizer results as predicates (#​864).
• Improved missing property handling (#​854).
• Handle invalid if conditions and detect null-byte crashes.
• Added regression tests for several reported issues.

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

[github-actions]

🔍 Dependency Review

github.com/expr-lang/expr v1.17.6 -> v1.17.7 — ✅ Safe

• Scope: Patch update within v1.17.
• Upstream review indicates only bug fixes and minor improvements; no breaking API changes between v1.17.6 and v1.17.7.
• This module is currently an indirect dependency in your project.

Relevant upstream references:

• Releases: https://github.com/expr-lang/expr/releases/tag/v1.17.7
• Compare: expr-lang/expr@v1.17.6...v1.17.7

Impact on your code:

• No public API changes or behavior changes that require code modifications were introduced in this patch.
• No configuration or evaluator interfaces changed.
• No changes needed in your codebase.

Suggested validation:

• Run existing tests that evaluate expressions (if any), especially around edge cases (nil handling, map/slice indexing, type assertions, operator precedence), to confirm expected behavior after the bug fixes.

Code changes required:

• None.

Notes

• Only one indirect dependency changed. No further action required.