VDB

CVE-2025-29786

CVE-2025-29786 PUBLISHED CVSS 7.5 HIGH

Memory Exhaustion in Expr Parser with Unrestricted Input

Reported by github_m · Published March 17, 2025

github.com/expr-lang/expr is fixed in 1.17.0 (Go Modules)

Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr expression parser is given an unbounded input string, it will attempt to compile the entire string and generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size isn’t limited, a malicious or inadvertent extremely large expression can consume excessive memory as the parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM) crash of the process. This issue is relatively uncommon and will only manifest when there are no restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In typical use cases where inputs are bounded or validated, this problem would not occur. The problem has been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the number of AST nodes and memory usage during parsing, preventing any single expression from exhausting resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In practice, this means validating or limiting the length of expression strings that your application will accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
github.com/expr-lang/exprGo Modules1.17.0
argo-rolloutsChainguard1.9.0-r1
argo-workflowsChainguard3.6.5-r2
corednsChainguard1.12.0-r9
keda-2.15Wolfi2.15.1-r14
eks-distro-fips-1.30Chainguard1.30.27-r2
keda-2.16Wolfi2.16.1-r8
argo-cd-2.14Wolfi2.14.5-r4
k8sgptWolfi0.4.1-r1
grafana-alloyChainguard1.7.4-r2
opentelemetry-collectorChainguard0.122.1-r0
tempo-fipsChainguard2.7.1-r4

19 more packages have a fixed version. See every fix in Lookup.

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

VendorProductVersions
expr-langexpr< 1.17.0
chainguardargo-rollouts0
chainguardargo-workflows0
chainguardcoredns0
wolfikeda-2.150
chainguardeks-distro-fips-1.300
wolfikeda-2.160
wolfiargo-cd-2.140
wolfik8sgpt0
chainguardgrafana-alloy0
chainguardopentelemetry-collector0
chainguardtempo-fips0
chainguardargo-cd-fips-3.00
chainguardargo-cd-2.130
chainguardeks-distro-1.320
wolfinats0
wolfikargo0
wolfiopentelemetry-collector0
chainguardeks-distro-1.300
wolfikeda-2.140

…and 45 more

Timeline

  • Mar 17, 2025 CVE Published
  • Mar 18, 2025 EPSS Score (30 in total, the first dated here)
  • Jun 1, 2026 Security Advisory (2 in total, the first dated here)
  • Jun 14, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-29786
vulnetix vdb fixes CVE-2025-29786

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-29786/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›