<?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-18T06:07:46.328965+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:2021-03386</id>
    <title>bdu:2021-03386</title>
    <updated>2026-10-18T06:07:46.333381+00:00</updated>
    <content>bdu:2021-03386</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2021-03386"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-minio-2021-21362</id>
    <title>BIT-minio-2021-21362 — Bypassing readOnly policy by creating a temporary 'mc share upload' URL</title>
    <updated>2026-10-18T06:07:46.333474+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: minio</p>
<p>MinIO is an open-source high performance object storage service and it is API compatible with Amazon S3 cloud storage service. In MinIO before version RELEASE.2021-03-04T00-53-13Z it is possible to bypass a readOnly policy by creating a temporary 'mc share upload' URL. Everyone is impacted who uses MinIO multi-users. This is fixed in version RELEASE.2021-03-04T00-53-13Z. As a workaround, one can disable uploads with `Content-Type: multipart/form-data` as mentioned in the S3 API RESTObjectPOST docs by using a proxy in front of MinIO.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-minio-2021-21362"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2021-avi-490</id>
    <title>certfr-2021-avi-490 — De multiples vulnérabilités ont été découvertes dans IBM Spectrum
Protect. Certaines d'entre elles permettent à un atta…</title>
    <updated>2026-10-18T06:07:46.333532+00:00</updated>
    <content>certfr-2021-avi-490</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2021-avi-490"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-22146</id>
    <title>EUVD-2026-22146</title>
    <updated>2026-10-18T06:07:46.333558+00:00</updated>
    <content>EUVD-2026-22146</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-22146"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-21362</id>
    <title>fkie_cve-2021-21362</title>
    <updated>2026-10-18T06:07:46.333575+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>MinIO is an open-source high performance object storage service and it is API compatible with Amazon S3 cloud storage service. In MinIO before version RELEASE.2021-03-04T00-53-13Z it is possible to bypass a readOnly policy by creating a temporary 'mc share upload' URL. Everyone is impacted who uses MinIO multi-users. This is fixed in version RELEASE.2021-03-04T00-53-13Z. As a workaround, one can disable uploads with `Content-Type: multipart/form-data` as mentioned in the S3 API RESTObjectPOST docs by using a proxy in front of MinIO.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-21362"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-21362</id>
    <title>gsd-2021-21362</title>
    <updated>2026-10-18T06:07:46.333609+00:00</updated>
    <content>gsd-2021-21362</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-21362"/>
  </entry>
</feed>
