<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 03 Nov 2026 06:34:26 +0000</lastBuildDate>
    <item>
      <title>GHSA-cfpf-hrx2-8rv6 — Expr has Denial of Service via Unbounded Recursion in Builtin Functions</title>
      <link>https://db.gcve.eu/vuln/ghsa-cfpf-hrx2-8rv6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/expr-lang/expr&lt;/p&gt;
&lt;p&gt;Several builtin functions in Expr, including `flatten`, `min`, `max`, `mean`, and `median`, perform
recursive traversal over user-provided data structures without enforcing a maximum recursion depth.&lt;/p&gt;
&lt;p&gt;If the evaluation environment contains **deeply nested** or **cyclic** data structures, these functions may recurse
indefinitely until exceed the Go runtime stack limit. This results in a **stack overflow panic**, causing the host
application to crash.&lt;/p&gt;
&lt;p&gt;While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness.
Instead of returning a recoverable evaluation error, the process may terminate unexpectedly.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently
validated data structures can lead to a **process-level crash** due to stack exhaustion.&lt;/p&gt;
&lt;p&gt;This issue is most relevant in scenarios where:&lt;/p&gt;
&lt;p&gt;* Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.
* Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.
* There are no application-level safeguards preventing deeply nested input data.&lt;/p&gt;
&lt;p&gt;In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting
panic can be used to reliably crash the a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/expr-lang/expr&lt;/p&gt;
&lt;p&gt;Several builtin functions in Expr, including `flatten`, `min`, `max`, `mean`, and `median`, perform
recursive traversal over user-provided data structures without enforcing a maximum recursion depth.&lt;/p&gt;
&lt;p&gt;If the evaluation environment contains **deeply nested** or **cyclic** data structures, these functions may recurse
indefinitely until exceed the Go runtime stack limit. This results in a **stack overflow panic**, causing the host
application to crash.&lt;/p&gt;
&lt;p&gt;While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness.
Instead of returning a recoverable evaluation error, the process may terminate unexpectedly.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently
validated data structures can lead to a **process-level crash** due to stack exhaustion.&lt;/p&gt;
&lt;p&gt;This issue is most relevant in scenarios where:&lt;/p&gt;
&lt;p&gt;* Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.
* Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.
* There are no application-level safeguards preventing deeply nested input data.&lt;/p&gt;
&lt;p&gt;In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting
panic can be used to reliably crash the a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-cfpf-hrx2-8rv6</guid>
    </item>
  </channel>
</rss>
