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.
CVE-2025-29786
“—” beside the score: it is equal to NVD's CVSS score.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-03-17. NVD baseline CVSS 7.5; sources differ by 0.0.
Also known asEUVD-2025-6527 (ENISA EUVD) · GHSA-93mq-9ffx-83m2 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 49th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
March 17, 2025
Last Modified
April 15, 2026
Advisory Details (3)
Auto-updated Oct 18, 2026Memory Exhaustion in Expr Parser with Unrestricted Input · Advisory · expr-lang/expr · GitHub
https://github.com/expr-lang/expr/security/advisories/GHSA-93mq-9ffx-83m2feat: add node budget and memory limits
Patch available: expr-lang/expr v1.17.0 (PR #762 merged 2025-03-07)
https://github.com/expr-lang/expr/pull/762commit 0d1944145442 (expr-lang/expr)
Patch available: expr-lang/expr v1.17.0 (contains commit 0d1944145442)
https://github.com/expr-lang/expr/commit/0d19441454426d2f58edb22c31f3ba5f99c7a26eVendor Advisories for CVE-2025-29786(10)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2025-29786Microsoft Security Response Center (MSRC)High
Memory Exhaustion in Expr Parser with Unrestricted Input
- RHSA-2025:9167Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.6.0 release
- RHSA-2025:7753Red Hat Product SecurityHigh
Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps v1.15.2 security update
- RHSA-2025:7479Red Hat Product SecurityHigh
Red Hat Security Advisory: opentelemetry-collector security update
- RHSA-2025:7407Red Hat Product SecurityHigh
Red Hat Security Advisory: opentelemetry-collector security update
- RHSA-2025:3993Red Hat Product SecurityHigh
Red Hat Security Advisory: Custom Metrics Autoscaler Operator for Red Hat OpenShift 2.15.1-6 Update
- RHSA-2025:3743Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.5.1 release
- RHSA-2025:3740Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 release
- +2 more
Patch Availability(10)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | rhosdt/opentelemetry-rhel8-operator:rhosdt-3.6-1749565051 | 2025-06-17 | redhat |
| redhat | openshift-gitops-1/must-gather-rhel8:v1.15.2-4 | 2025-05-15 | redhat |
| redhat | opentelemetry-collector-0:0.107.0-9.el10_0 | 2025-05-13 | redhat |
| redhat | opentelemetry-collector-0:0.107.0-8.el9_6 | 2025-05-13 | redhat |
| redhat | custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9:2.15.1-1744845044 | 2025-04-17 | redhat |
| redhat | rhosdt/tempo-rhel8:rhosdt-3.5-1744102053 | 2025-04-09 | redhat |
| redhat | rhosdt/opentelemetry-collector-rhel8:rhosdt-3.5-1744103234 | 2025-04-09 | redhat |
| redhat | opentelemetry-collector-0:0.107.0-7.el9_4 | 2025-04-03 | redhat |
| redhat | opentelemetry-collector-0:0.107.0-8.el9_5 | 2025-03-27 | redhat |
| go | github.com/expr-lang/expr @ 1.17.0 (fixes < 1.17.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-antonmedv-expr | 1.8.9-2 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-antonmedv-expr | 1.8.9-2 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-antonmedv-expr | 1.8.9-2 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-antonmedv-expr | 1.8.9-2 |
| — |
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/expr-lang/expr | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 43× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 96 of 232 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 136 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-11-01 08:07 UTCGHSA enrichmentGHSA-93mq-9ffx-83m2 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-01 08:07 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-27 17:51 UTCEG score recompute
- 2026-10-27 17:51 UTCVendor advisory
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-25 16:37 UTCEG score recompute
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-18 18:37 UTCEG score recompute
- 2026-10-18 18:37 UTCVendor advisory
- 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-18 05:40 UTCEG score recompute
- 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
Show 71 moreShow fewer
- 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-12 17:13 UTCEG score recompute
- 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-11 20:45 UTCEG score recompute
- 2026-10-11 18:56 UTCEG score recompute
- 2026-10-11 15:33 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-06 23:25 UTCOSV refresh
- 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-29 15:19 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-17 05:06 UTCOSV refresh
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-29 05:13 UTCOSV refresh
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-08-12 17:13 UTCOSV refresh
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.6% · 44th percentile
Related CVEs(same product + same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2025:3335 · redhat:RHSA-2025:3740 · redhat:RHSA-2025:7753
Frequently asked(5)
What is CVE-2025-29786?
When was the CVE record for CVE-2025-29786 published?
Is CVE-2025-29786 actively exploited?
What is the CVSS score of CVE-2025-29786?
How do I remediate CVE-2025-29786?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-29786
Is Your Infrastructure Affected by CVE-2025-29786?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.