Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Memory Exhaustion in Expr Parser with Unrestricted Input

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/expr-lang/expr 1.17.0osv · severity unknownFixed by github.com/expr-lang/expr 1.17.0KEV status unknown

cve-program · CVE-2025-29786

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-6527

Published

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.

Read the publisher's advisory

nvd · CVE-2025-29786

Published

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.

Read the publisher's advisory

osv · GHSA-93mq-9ffx-83m2

Published

### Impact 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. ### Patches 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. ### Workarounds 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, you 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. ### References - #762

Read the publisher's advisory

osv · GO-2025-3525

Published

Memory Exhaustion in Expr Parser with Unrestricted Input in github.com/expr-lang/expr

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-29786

Published

expr

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "expr-lang",
                    "product": "expr",
                    "versions": [
                        {
                            "version": "< 1.17.0",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-6527

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 17, 2025, 1:15:32 PM

dateUpdated: Jan 23, 2026, 4:29:26 PM

12 related source bulletins · separate from aliases

RHSA-2025:3743: Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.5.1 release

CVE-2025-22868 · CVE-2025-27144 · CVE-2025-29786 · CVE-2025-30204

RHSA-2025:7479: Red Hat Security Advisory: opentelemetry-collector security update

CVE-2025-22868 · CVE-2025-27144 · CVE-2025-29786 · CVE-2025-30204

RHSA-2025:7753: Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps v1.15.2 security update

CVE-2023-45288 · CVE-2024-13484 · CVE-2024-57083 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-27144 · CVE-2025-29786 · CVE-2025-30204

RHSA-2025:3740: Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 release

CVE-2025-2786 · CVE-2025-2842 · CVE-2025-22868 · CVE-2025-29786 · CVE-2025-30204

openSUSE-SU-2025:15006-1: argocd-cli-2.14.10-1.1 on GA media

CVE-2025-29786

msrc_CVE-2025-29786: Memory Exhaustion in Expr Parser with Unrestricted Input

CVE-2025-29786

RHSA-2025:3335: Red Hat Security Advisory: opentelemetry-collector security update

CVE-2024-45336 · CVE-2025-22868 · CVE-2025-27144 · CVE-2025-29786

RHSA-2025:3593: Red Hat Security Advisory: opentelemetry-collector security update

CVE-2024-45336 · CVE-2025-22868 · CVE-2025-27144 · CVE-2025-29786

RHSA-2025:9167: Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.6.0 release

CVE-2025-22868 · CVE-2025-27144 · CVE-2025-29786 · CVE-2025-30204

RHSA-2025:3993: Red Hat Security Advisory: Custom Metrics Autoscaler Operator for Red Hat OpenShift 2.15.1-6 Update

CVE-2025-29786 · CVE-2025-30204

RHSA-2025:7407: Red Hat Security Advisory: opentelemetry-collector security update

CVE-2025-22868 · CVE-2025-27144 · CVE-2025-29786 · CVE-2025-30204

openSUSE-SU-2025:14910-1: govulncheck-vulndb-0.0.20250318T181448-1.1 on GA media

CVE-2024-40635 · CVE-2025-0495 · CVE-2025-2241 · CVE-2025-29781 · CVE-2025-29786

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-29786

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-770

Original publisher date fields

published: 2025-03-17T14:15:22.237

lastModified: 2026-06-17T09:05:40.147

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-93mq-9ffx-83m2

Published

github.com/expr-lang/expr

Go

SEMVER · introduced 0 → fixed 1.17.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2025-3525

Published

github.com/expr-lang/expr

Go

SEMVER · introduced 0 → fixed 1.17.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 12:50 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current