<?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-07T19:40:59.101088+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-nifi-2020-9491</id>
    <title>BIT-nifi-2020-9491</title>
    <updated>2026-10-07T19:40:59.167767+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: nifi</p>
<p>In Apache NiFi 1.2.0 to 1.11.4, the NiFi UI and API were protected by mandating TLS v1.2, as well as listening connections established by processors like ListenHTTP, HandleHttpRequest, etc. However intracluster communication such as cluster request replication, Site-to-Site, and load balanced queues continued to support TLS v1.0 or v1.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-nifi-2020-9491"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-39162</id>
    <title>EUVD-2026-39162</title>
    <updated>2026-10-07T19:40:59.167831+00:00</updated>
    <content>EUVD-2026-39162</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-39162"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-9491</id>
    <title>fkie_cve-2020-9491</title>
    <updated>2026-10-07T19:40:59.167848+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>In Apache NiFi 1.2.0 to 1.11.4, the NiFi UI and API were protected by mandating TLS v1.2, as well as listening connections established by processors like ListenHTTP, HandleHttpRequest, etc. However intracluster communication such as cluster request replication, Site-to-Site, and load balanced queues continued to support TLS v1.0 or v1.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-9491"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-rfmp-jvr7-hx78</id>
    <title>GHSA-rfmp-jvr7-hx78 — Inadequate Encryption Strength in Apache NiFi</title>
    <updated>2026-10-07T19:40:59.167873+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.apache.nifi:nifi</p>
<p>In Apache NiFi 1.2.0 to 1.11.4, the NiFi UI and API were protected by mandating TLS v1.2, as well as listening connections established by processors like ListenHTTP, HandleHttpRequest, etc. However intracluster communication such as cluster request replication, Site-to-Site, and load balanced queues continued to support TLS v1.0 or v1.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-rfmp-jvr7-hx78"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-9491</id>
    <title>gsd-2020-9491</title>
    <updated>2026-10-07T19:40:59.167895+00:00</updated>
    <content>gsd-2020-9491</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-9491"/>
  </entry>
</feed>
