<?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-06T04:17:55.624510+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/bdu:2026-02444</id>
    <title>bdu:2026-02444</title>
    <updated>2026-10-06T04:17:55.674334+00:00</updated>
    <content>bdu:2026-02444</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-02444"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-nifi-2026-25903</id>
    <title>BIT-nifi-2026-25903 — Apache NiFi: Missing Authorization of Restricted Permissions for Component Updates</title>
    <updated>2026-10-06T04:17:55.674380+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: nifi</p>
<p>Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on extension components that have specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required to add the annotated component to the flow configuration, but framework authorization did not check restricted status when updating a component previously added. The missing authorization requires a more privileged user to add a restricted component to the flow configuration, but permits a less privileged user to make property configuration changes. Apache NiFi installations that do not implement different levels of authorization for Restricted components are not subject to this vulnerability because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.8.0 is the recommended mitigation.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-nifi-2026-25903"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-bq50387</id>
    <title>Withdrawn: CLEANSTART-2026-BQ50387 — Security fixes in apache-nifi 2.6.0-r3</title>
    <updated>2026-10-06T04:17:55.674451+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> CleanStart: apache-nifi</p>
<p>Package apache-nifi version 2.6.0-r3 fixes 51 vulnerabilities: CVE-2024-29371, CVE-2024-45993, CVE-2025-8671, CVE-2025-11143, CVE-2025-31344...</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-bq50387"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-268673</id>
    <title>EUVD-2026-268673</title>
    <updated>2026-10-06T04:17:55.674478+00:00</updated>
    <content>EUVD-2026-268673</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-268673"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-25903</id>
    <title>fkie_cve-2026-25903</title>
    <updated>2026-10-06T04:17:55.674492+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on extension components that have specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required to add the annotated component to the flow configuration, but framework authorization did not check restricted status when updating a component previously added. The missing authorization requires a more privileged user to add a restricted component to the flow configuration, but permits a less privileged user to make property configuration changes. Apache NiFi installations that do not implement different levels of authorization for Restricted components are not subject to this vulnerability because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.8.0 is the recommended mitigation.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-25903"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-c5w7-m8wf-xc77</id>
    <title>GHSA-c5w7-m8wf-xc77 — Apache NiFi: Missing Authorization of Restricted Permissions for Component Updates</title>
    <updated>2026-10-06T04:17:55.674518+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.apache.nifi:nifi-web-api</p>
<p>Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on extension components that have specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required to add the annotated component to the flow configuration, but framework authorization did not check restricted status when updating a component previously added. The missing authorization requires a more privileged user to add a restricted component to the flow configuration, but permits a less privileged user to make property configuration changes. Apache NiFi installations that do not implement different levels of authorization for Restricted components are not subject to this vulnerability because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.8.0 is the recommended mitigation.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-c5w7-m8wf-xc77"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0430</id>
    <title>WID-SEC-W-2026-0430 — Apache Nifi: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
    <updated>2026-10-06T04:17:55.674543+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann eine Schwachstelle in Apache Nifi ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0430"/>
  </entry>
</feed>
