{"id":"EUVD-2025-6527","revision":null,"records":[{"revision":"8eb8b31cdd764097803f0b0453eb1d10","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2025-29786","aliases":[],"title":"Memory Exhaustion in Expr Parser with Unrestricted Input","description":"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.","state":0,"publishedAt":"2025-03-17T13:15:32.836+00:00","modifiedAt":"2026-01-23T16:29:26.719+00:00","affected":[{"ecosystem":"Vendor product","name":"expr","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"expr-lang\",\n                    \"product\": \"expr\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 1.17.0\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","score":7.5,"severity":"HIGH"}],"references":["https://github.com/expr-lang/expr/security/advisories/GHSA-93mq-9ffx-83m2","https://github.com/expr-lang/expr/pull/762","https://github.com/expr-lang/expr/commit/0d19441454426d2f58edb22c31f3ba5f99c7a26e"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-29786","license":"CVE Program Terms of Use","key":"cve-program:CVE-2025-29786","identifiers":["CVE-2025-29786"]},"retained":false,"historicalAffected":[]},{"revision":"df6c13a3f76c4d47a88871b4182be10f","observedAt":"2026-11-15T03:40:13.101+00:00","statement":{"source":"euvd","id":"EUVD-2025-6527","aliases":["CVE-2025-29786","GHSA-93mq-9ffx-83m2"],"title":"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…","description":"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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","score":7.5,"severity":null}],"references":["https://github.com/expr-lang/expr/security/advisories/GHSA-93mq-9ffx-83m2","https://github.com/expr-lang/expr/pull/762","https://github.com/expr-lang/expr/commit/0d19441454426d2f58edb22c31f3ba5f99c7a26e"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-6527","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Mar 17, 2025, 1:15:32 PM","dateUpdated":"Jan 23, 2026, 4:29:26 PM"},"relatedAdvisories":[{"id":"RHSA-2025:3743","title":"Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.5.1 release","vulnerabilityIds":["CVE-2025-22868","CVE-2025-27144","CVE-2025-29786","CVE-2025-30204"]},{"id":"RHSA-2025:7479","title":"Red Hat Security Advisory: opentelemetry-collector security update","vulnerabilityIds":["CVE-2025-22868","CVE-2025-27144","CVE-2025-29786","CVE-2025-30204"]},{"id":"RHSA-2025:7753","title":"Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps v1.15.2 security update","vulnerabilityIds":["CVE-2023-45288","CVE-2024-13484","CVE-2024-57083","CVE-2025-22868","CVE-2025-22869","CVE-2025-27144","CVE-2025-29786","CVE-2025-30204"]},{"id":"RHSA-2025:3740","title":"Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 release","vulnerabilityIds":["CVE-2025-2786","CVE-2025-2842","CVE-2025-22868","CVE-2025-29786","CVE-2025-30204"]},{"id":"openSUSE-SU-2025:15006-1","title":"argocd-cli-2.14.10-1.1 on GA media","vulnerabilityIds":["CVE-2025-29786"]},{"id":"msrc_CVE-2025-29786","title":"Memory Exhaustion in Expr Parser with Unrestricted Input","vulnerabilityIds":["CVE-2025-29786"]},{"id":"RHSA-2025:3335","title":"Red Hat Security Advisory: opentelemetry-collector security update","vulnerabilityIds":["CVE-2024-45336","CVE-2025-22868","CVE-2025-27144","CVE-2025-29786"]},{"id":"RHSA-2025:3593","title":"Red Hat Security Advisory: opentelemetry-collector security update","vulnerabilityIds":["CVE-2024-45336","CVE-2025-22868","CVE-2025-27144","CVE-2025-29786"]},{"id":"RHSA-2025:9167","title":"Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.6.0 release","vulnerabilityIds":["CVE-2025-22868","CVE-2025-27144","CVE-2025-29786","CVE-2025-30204"]},{"id":"RHSA-2025:3993","title":"Red Hat Security Advisory: Custom Metrics Autoscaler Operator for Red Hat OpenShift 2.15.1-6 Update","vulnerabilityIds":["CVE-2025-29786","CVE-2025-30204"]},{"id":"RHSA-2025:7407","title":"Red Hat Security Advisory: opentelemetry-collector security update","vulnerabilityIds":["CVE-2025-22868","CVE-2025-27144","CVE-2025-29786","CVE-2025-30204"]},{"id":"openSUSE-SU-2025:14910-1","title":"govulncheck-vulndb-0.0.20250318T181448-1.1 on GA media","vulnerabilityIds":["CVE-2024-40635","CVE-2025-0495","CVE-2025-2241","CVE-2025-29781","CVE-2025-29786"]}],"note":"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."},"key":"euvd:EUVD-2025-6527","identifiers":["EUVD-2025-6527","CVE-2025-29786","GHSA-93mq-9ffx-83m2"]},"retained":false,"historicalAffected":[]},{"revision":"498d60bf90654fd49532984c3eb9a548","observedAt":"2026-10-25T02:24:42.386+00:00","statement":{"source":"nvd","id":"CVE-2025-29786","aliases":[],"title":"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…","description":"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.","state":0,"publishedAt":"2025-03-17T14:15:22.237+00:00","modifiedAt":"2026-06-17T09:05:40.147+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","score":7.5,"severity":"HIGH"}],"references":["https://github.com/expr-lang/expr/commit/0d19441454426d2f58edb22c31f3ba5f99c7a26e","https://github.com/expr-lang/expr/pull/762","https://github.com/expr-lang/expr/security/advisories/GHSA-93mq-9ffx-83m2"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2025-29786","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Deferred","weaknesses":["CWE-770"],"productCriteria":[],"sourceDates":{"published":"2025-03-17T14:15:22.237","lastModified":"2026-06-17T09:05:40.147"},"relatedAdvisories":[],"note":"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."},"key":"nvd:CVE-2025-29786","identifiers":["CVE-2025-29786"]},"retained":false,"historicalAffected":[]},{"revision":"23d51e6a314b46dfaa379bee192b329b","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-93mq-9ffx-83m2","aliases":["CVE-2025-29786","GO-2025-3525"],"title":"Memory Exhaustion in Expr Parser with Unrestricted Input","description":"### Impact\nIf 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.\n\n### Patches\n\nThe 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.\n\n### Workarounds\n\nFor 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.\n\n### References\n\n- #762","state":0,"publishedAt":"2025-03-17T21:26:22+00:00","modifiedAt":"2026-09-10T03:50:22.9682894+00:00","affected":[{"ecosystem":"Go","name":"github.com/expr-lang/expr","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.17.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/expr-lang/expr/security/advisories/GHSA-93mq-9ffx-83m2","https://nvd.nist.gov/vuln/detail/CVE-2025-29786","https://github.com/expr-lang/expr/pull/762","https://github.com/expr-lang/expr/commit/0d19441454426d2f58edb22c31f3ba5f99c7a26e","https://github.com/expr-lang/expr"],"sourceUrl":"https://github.com/advisories/GHSA-93mq-9ffx-83m2","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-93mq-9ffx-83m2","identifiers":["GHSA-93mq-9ffx-83m2","CVE-2025-29786","GO-2025-3525"]},"retained":false,"historicalAffected":[]},{"revision":"5231c130996a4b5f97a33a535411a906","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2025-3525","aliases":["CVE-2025-29786","GHSA-93mq-9ffx-83m2"],"title":"Memory Exhaustion in Expr Parser with Unrestricted Input in github.com/expr-lang/expr","description":"Memory Exhaustion in Expr Parser with Unrestricted Input in github.com/expr-lang/expr","state":0,"publishedAt":"2025-03-18T16:33:22+00:00","modifiedAt":"2026-02-04T03:29:30.221101+00:00","affected":[{"ecosystem":"Go","name":"github.com/expr-lang/expr","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.17.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/expr-lang/expr/security/advisories/GHSA-93mq-9ffx-83m2","https://github.com/expr-lang/expr/commit/0d19441454426d2f58edb22c31f3ba5f99c7a26e","https://github.com/expr-lang/expr/pull/762"],"sourceUrl":"https://osv.dev/vulnerability/GO-2025-3525","license":"OSV · upstream source license applies","key":"osv:GO-2025-3525","identifiers":["GO-2025-3525","CVE-2025-29786","GHSA-93mq-9ffx-83m2"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-16T12:44:53.7069159+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T12:44:53.7069159+00:00","lastSuccessAt":"2026-11-16T12:44:53.850219+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.8502206+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-6be044d0e08779dadd136f949a536de4047af96f5d7bceb7e190ecffbb8f18ca-237c53704f95a87effe0a1147a1bcf3cd93376e65fa4303e1b86b3915f8b7c7a","complete":true,"records":425970,"lastAttemptAt":"2026-11-16T12:44:53.412921+00:00","lastSuccessAt":"2026-11-16T12:44:53.3189092+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.412921+00:00","snapshotPublishedAt":"2026-11-16T12:28:00+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-ea8954ba9b8a4f759f7e51e8bc4698ca","complete":false,"records":13821,"lastAttemptAt":"2026-11-16T12:46:28.5866342+00:00","lastSuccessAt":"2026-11-16T12:46:28.582+00:00","error":"5 identifier lookups failed; latest failures include AccessDenied (HTTP 403). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T12:46:28.582+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13869,"expectedIdentifiers":13874,"failedIdentifiers":5},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-16T12:44:53.7069159+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T12:44:53.7069159+00:00","lastSuccessAt":"2026-11-16T12:44:53.8509796+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.85098+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-1ca26f249fe448ada48a3a7b82aa64d9","complete":false,"records":13833,"lastAttemptAt":"2026-11-16T12:45:56.1167563+00:00","lastSuccessAt":"2026-11-16T12:45:56.113+00:00","error":"400 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T12:45:56.113+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13474,"expectedIdentifiers":13874,"failedIdentifiers":400},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-16T12:44:53.6598825+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.6598825+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-16T12:44:53.4548081+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.4548081+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-16T12:44:53.6730048+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.6730048+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-263d9c8d63997345727b11314d9b9377eba9fd4146f04497c069a15e332b60cb","complete":true,"records":232482,"lastAttemptAt":"2026-11-16T12:44:53.5565665+00:00","lastSuccessAt":"2026-11-16T07:32:30.5701252+00:00","error":null,"lastVerifiedAt":"2026-11-16T12:44:53.5565665+00:00","snapshotPublishedAt":"2026-11-16T06:48:00+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}