<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 14:58:13 +0000</lastBuildDate>
    <item>
      <title>certfr-2022-avi-860 — Une vulnérabilité a été découverte dans Pulse Connect Secure. Elle
permet à un attaquant de provoquer une exécution de…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2022-avi-860</link>
      <description>certfr-2022-avi-860</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2022-avi-860</guid>
    </item>
    <item>
      <title>EUVD-2026-13330</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-13330</link>
      <description>EUVD-2026-13330</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-13330</guid>
    </item>
    <item>
      <title>fkie_cve-2022-21826</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-21826</link>
      <description>&lt;p&gt;Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request&amp;#39;s Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down that connection, this means when someone loads website attacker may be able to make browser issue a POST to the application, enabling XSS.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request&amp;#39;s Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down that connection, this means when someone loads website attacker may be able to make browser issue a POST to the application, enabling XSS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-21826</guid>
    </item>
    <item>
      <title>GHSA-w594-hmpv-qhh5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w594-hmpv-qhh5</link>
      <description>&lt;p&gt;Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request&amp;#39;s Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down that connection, this means when someone loads website attacker may be able to make browser issue a POST to the application, enabling XSS.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request&amp;#39;s Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down that connection, this means when someone loads website attacker may be able to make browser issue a POST to the application, enabling XSS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w594-hmpv-qhh5</guid>
    </item>
    <item>
      <title>gsd-2022-21826</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-21826</link>
      <description>gsd-2022-21826</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-21826</guid>
    </item>
  </channel>
</rss>
