<?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-03T07:14:53.158071+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/euvd-2026-171425</id>
    <title>EUVD-2026-171425</title>
    <updated>2026-10-03T07:14:53.234930+00:00</updated>
    <content>EUVD-2026-171425</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-171425"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36781</id>
    <title>fkie_cve-2022-36781</title>
    <updated>2026-10-03T07:14:53.234975+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>ConnectWise ScreenConnect versions 22.6 and below contained a flaw allowing potential brute force attacks on custom access tokens due to inadequate rate-limiting controls in the default configuration. Attackers could exploit this vulnerability to gain unauthorized access by repeatedly attempting access code combinations. ConnectWise has addressed this issue in later versions by implementing rate-limiting controls as a preventive measure against brute force attacks.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-36781"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9xh6-8fcg-f9qm</id>
    <title>GHSA-9xh6-8fcg-f9qm</title>
    <updated>2026-10-03T07:14:53.235023+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WiseConnect - ScreenConnect Session Code Bypass. An attacker would have to use a proxy to monitor the traffic, and perform a brute force on the session code in order to get in. Sensitive data about the company , get in a session.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9xh6-8fcg-f9qm"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-36781</id>
    <title>gsd-2022-36781</title>
    <updated>2026-10-03T07:14:53.235051+00:00</updated>
    <content>gsd-2022-36781</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-36781"/>
  </entry>
</feed>
