<?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-06T06:09:40.225563+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-25011</id>
    <title>CVE-2025-25011 — Beats Uncontrolled Search Path Element can lead to Local Privilege Escalation (LPE) when using the Windows Installer</title>
    <updated>2026-10-06T06:09:40.275934+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Elastic Beats</p>
<p>An uncontrolled search path element vulnerability can lead to local privilege Escalation (LPE) via Insecure Directory Permissions. The vulnerability arises from improper handling of directory permissions. An attacker with local access may exploit this flaw to move and delete arbitrary files, potentially gaining SYSTEM privileges.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-25011"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-32fw-gq77-f2f2</id>
    <title>GHSA-32fw-gq77-f2f2 — Eclipse Paho Go MQTT may incorrectly encode strings if length exceeds 65535 bytes</title>
    <updated>2026-10-06T06:09:40.276012+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/eclipse/paho.mqtt.golang</p>
<p>In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions &lt;=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet).</p>
<p>The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-32fw-gq77-f2f2"/>
  </entry>
</feed>
