<?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-10-27T13:20:57.031723+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/bit-elasticsearch-2026-102411</id>
    <title>BIT-elasticsearch-2026-102411 — Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of Service</title>
    <updated>2026-10-27T13:20:57.036459+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: elasticsearch</p>
<p>Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to Denial of Service via Excessive Allocation (CAPEC-130). Elasticsearch enforces a size limit on the user-supplied metadata field for each individual template resource, but does not limit the total memory used when multiple such resources are retrieved together. A user holding the *manage_index_templates* cluster privilege can register multiple resources each within the individual limit. Retrieving them together materializes all of their metadata values in memory at once, exhausting available heap and causing the affected node to fail with an out-of-memory error, resulting in a denial of service.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-elasticsearch-2026-102411"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1276</id>
    <title>certfr-2026-avi-1276 — De multiples vulnérabilités ont été découvertes dans les produits Elastic. Certaines d'entre elles permettent à un atta…</title>
    <updated>2026-10-27T13:20:57.036508+00:00</updated>
    <content>certfr-2026-avi-1276</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1276"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-jz62196</id>
    <title>CLEANSTART-2026-JZ62196 — Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to Denial of Service via Exces…</title>
    <updated>2026-10-27T13:20:57.036528+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: sonarqube</p>
<p>CVE-2026-102411 affects multiple packages. Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to Denial of Service via Excessive Allocation (CAPEC-130). See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-jz62196"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-384007</id>
    <title>EUVD-2026-384007</title>
    <updated>2026-10-27T13:20:57.036549+00:00</updated>
    <content>EUVD-2026-384007</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-384007"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-102411</id>
    <title>fkie_cve-2026-102411</title>
    <updated>2026-10-27T13:20:57.036561+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to Denial of Service via Excessive Allocation (CAPEC-130). Elasticsearch enforces a size limit on the user-supplied metadata field for each individual template resource, but does not limit the total memory used when multiple such resources are retrieved together. A user holding the *manage_index_templates* cluster privilege can register multiple resources each within the individual limit. Retrieving them together materializes all of their metadata values in memory at once, exhausting available heap and causing the affected node to fail with an out-of-memory error, resulting in a denial of service.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-102411"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qvfh-5p79-6753</id>
    <title>GHSA-qvfh-5p79-6753</title>
    <updated>2026-10-27T13:20:57.036583+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to Denial of Service via Excessive Allocation (CAPEC-130). Elasticsearch enforces a size limit on the user-supplied metadata field for each individual template resource, but does not limit the total memory used when multiple such resources are retrieved together. A user holding the *manage_index_templates* cluster privilege can register multiple resources each within the individual limit. Retrieving them together materializes all of their metadata values in memory at once, exhausting available heap and causing the affected node to fail with an out-of-memory error, resulting in a denial of service.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qvfh-5p79-6753"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-102411</id>
    <title>msrc_CVE-2026-102411 — Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of Service</title>
    <updated>2026-10-27T13:20:57.036599+00:00</updated>
    <content>msrc_CVE-2026-102411</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-102411"/>
  </entry>
</feed>
