<?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-05T23:37:48.505608+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-15681</id>
    <title>EUVD-2026-15681</title>
    <updated>2026-10-05T23:37:48.508665+00:00</updated>
    <content>EUVD-2026-15681</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-15681"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-28352</id>
    <title>fkie_cve-2022-28352</title>
    <updated>2026-10-05T23:37:48.508696+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WeeChat (aka Wee Enhanced Environment for Chat) 3.2 to 3.4 before 3.4.1 does not properly verify the TLS certificate of the server, after certain GnuTLS options are changed, which allows man-in-the-middle attackers to spoof a TLS chat server via an arbitrary certificate. NOTE: this only affects situations where weechat.network.gnutls_ca_system or weechat.network.gnutls_ca_user is changed without a WeeChat restart.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-28352"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-q6x4-wf9q-6g23</id>
    <title>GHSA-q6x4-wf9q-6g23</title>
    <updated>2026-10-05T23:37:48.508727+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WeeChat (aka Wee Enhanced Environment for Chat) 3.2 to 3.4 before 3.4.1 does not properly verify the TLS certificate of the server, after certain GnuTLS options are changed, which allows man-in-the-middle attackers to spoof a TLS chat server via an arbitrary certificate. NOTE: this only affects situations where weechat.network.gnutls_ca_system or weechat.network.gnutls_ca_user is changed without a WeeChat restart.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-q6x4-wf9q-6g23"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-28352</id>
    <title>gsd-2022-28352</title>
    <updated>2026-10-05T23:37:48.508745+00:00</updated>
    <content>gsd-2022-28352</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-28352"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-28352</id>
    <title>UBUNTU-CVE-2022-28352</title>
    <updated>2026-10-05T23:37:48.508756+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: weechat, Ubuntu:Pro:18.04:LTS: weechat, Ubuntu:Pro:20.04:LTS: weechat, Ubuntu:22.04:LTS: weechat</p>
<p>WeeChat (aka Wee Enhanced Environment for Chat) 3.2 to 3.4 before 3.4.1 does not properly verify the TLS certificate of the server, after certain GnuTLS options are changed, which allows man-in-the-middle attackers to spoof a TLS chat server via an arbitrary certificate. NOTE: this only affects situations where weechat.network.gnutls_ca_system or weechat.network.gnutls_ca_user is changed without a WeeChat restart.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-28352"/>
  </entry>
</feed>
