<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-18T10:28:36.124014+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-61726</id>
    <title>CVE-2025-61726 — Memory exhaustion in query parameter parsing in net/url</title>
    <updated>2026-11-18T10:28:36.142498+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go standard library net/url, Red Hat Cryostat 4 on RHEL 9, Red Hat HawtIO HawtIO 4.3.1, Red Hat HawtIO HawtIO 4.4.0, Red Hat Ansible Automation Platform 2.4 for RHEL 8, Red Hat Ansible Automation Platform 2.4 for RHEL 9, Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Ansible Automation Platform 2.6 for RHEL 10, Red Hat Ansible Automation Platform 2.6 for RHEL 9 and 152 more</p>
<p>The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-61726"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-cfpf-hrx2-8rv6</id>
    <title>GHSA-cfpf-hrx2-8rv6 — Expr has Denial of Service via Unbounded Recursion in Builtin Functions</title>
    <updated>2026-11-18T10:28:36.144208+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/expr-lang/expr</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>### Impact</p>
<p>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.</p>
<p>This issue is most relevant in scenarios where:</p>
<p>* 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.</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-cfpf-hrx2-8rv6"/>
  </entry>
</feed>
