CVE-2025-68156: Github.com/expr lang/expr Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-cfpf-hrx2-8rv6
CVSS 7.5
CWE-770
Published
Advisory Summary

CVE-2025-68156 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Github.com/expr lang/expr libraries in the Go ecosystem. The issue involves expr has denial of service via unbounded recursion in builtin functions. Remediation is available by upgrading affected packages to version 1.17.7.

CVE-2025-68156 at a Glance

CVE Identifier CVE-2025-68156
GHSA Identifier GHSA-cfpf-hrx2-8rv6
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Github.com/expr lang/expr
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2025-68156

To remediate this vulnerability, upgrade all affected Github.com/expr lang/expr dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/expr-lang/expr fixed: 1.17.7
Upgrade github.com/expr-lang/expr to 1.17.7
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/expr-lang/expr

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-68156, inspect your project dependencies for Github.com/expr lang/expr:

inspect dependencies for github.com/expr-lang/expr

Analyze the terminal output to locate any version of Github.com/expr lang/expr in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.17.7), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Github.com/expr lang/expr, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2025-68156 Affected Github.com/expr lang/expr Versions

1 component(s)
Fixed Versions:
1.17.7
Product / Package Ecosystem Affected Versions Fixed Version
github.com/expr-lang/expr
Go
< 1.17.7
1.17.7

References

Frequently Asked Questions

What is CVE-2025-68156?
CVE-2025-68156 is a security vulnerability in Github.com/expr lang/expr involving Expr has Denial of Service via Unbounded Recursion in Builtin Functions under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Github.com/expr lang/expr versions are affected?
Affected versions include releases prior to 1.17.7 across affected packages: github.com/expr-lang/expr.
What version fixes CVE-2025-68156?
Upgrading to 1.17.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/expr-lang/expr affected?
Yes, github.com/expr-lang/expr is affected in releases prior to 1.17.7. Upgrade your dependency to 1.17.7 or later.
What is the CVSS score of CVE-2025-68156?
CVE-2025-68156 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2025-68156?
CVE-2025-68156 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Go dependencies for CVE-2025-68156?
Run the dependency tree command: 'inspect dependencies for github.com/expr-lang/expr'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cfpf-hrx2-8rv6",
  "modified" : "2025-12-16T22:34:16Z",
  "published" : "2025-12-16T22:34:16Z",
  "aliases" : [ "CVE-2025-68156" ],
  "summary" : "Expr has Denial of Service via Unbounded Recursion in Builtin Functions",
  "details" : "Several builtin functions in Expr, including `flatten`, `min`, `max`, `mean`, and `median`, perform\nrecursive traversal over user-provided data structures without enforcing a maximum recursion depth.\n\nIf the evaluation environment contains **deeply nested** or **cyclic** data structures, these functions may recurse\nindefinitely until exceed the Go runtime stack limit. This results in a **stack overflow panic**, causing the host\napplication to crash.\n\nWhile exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the\nevaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness.\nInstead of returning a recoverable evaluation error, the process may terminate unexpectedly.\n\n### Impact\n\nIn affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently\nvalidated data structures can lead to a **process-level crash** due to stack exhaustion.\n\nThis issue is most relevant in scenarios where:\n\n* Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.\n* Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.\n* There are no application-level safeguards preventing deeply nested input data.\n\nIn typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting\npanic can be used to reliably crash the application, constituting a denial of service.\n\n### Patches\n\nThe issue has been fixed in the v1.17.7 versions of Expr.\n\nThe patch introduces a **maximum recursion depth limit** for affected builtin functions. When this limit is exceeded,\nevaluation aborts gracefully and returns a descriptive error instead of panicking.\n\nAdditionally, the maximum depth can be customized by users via `builtin.MaxDepth`, allowing applications with legitimate\ndeep structures to raise the limit in a controlled manner.\n\nUsers are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and\ncomprehensive test coverage to prevent regressions.\n\n### Workarounds\n\nFor users who cannot immediately upgrade, the following mitigations are recommended:\n\n* Ensure that evaluation environments cannot contain cyclic references.\n* Validate or sanitize externally supplied data structures before passing them to Expr.\n* Wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure).\n\nThese workarounds reduce risk but do not fully eliminate the issue without the patch.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/expr-lang/expr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.17.7"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/expr-lang/expr/security/advisories/GHSA-cfpf-hrx2-8rv6"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-68156"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/expr-lang/expr/pull/870"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/expr-lang/expr"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-16T22:34:16Z",
    "nvd_published_at" : "2025-12-16T19:16:00Z"
  }
}