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

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 (A…

Historical advisory saved 7 Nov 2026 01:32:35 UTC. The publisher may have updated it since then. Latest 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.

Additional publisher context

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

Source published
Mar 17, 2025, 1:15:32 PM (timezone not stated)
Source modified
Jan 23, 2026, 4:29:26 PM (timezone not stated)
Saved here
7 Nov 2026 01:32:35 UTC
Source terms
ENISA EUVD · source terms and attribution apply

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

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

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