<?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-03T06:38:35.223708+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-232700</id>
    <title>EUVD-2026-232700</title>
    <updated>2026-10-03T06:38:35.226795+00:00</updated>
    <content>EUVD-2026-232700</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-232700"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-24840</id>
    <title>fkie_cve-2022-24840</title>
    <updated>2026-10-03T06:38:35.226825+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>django-s3file is a lightweight file upload input for Django and Amazon S3 . In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the `AWS_LOCATION` setting was set, traversal was limited to that location only. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, prior to the release of the patch. The vulnerability has been fixed in version 5.5.1 and above. There is no feasible workaround. We must urge all users to immediately updated to a patched version.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-24840"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4w8f-hjm9-xwgf</id>
    <title>GHSA-4w8f-hjm9-xwgf — Path Traversal in django-s3file</title>
    <updated>2026-10-03T06:38:35.226858+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: django-s3file</p>
<p>### Impact</p>
<p>It was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files.
The issue was discovered by the maintainer. There were no reports of the vulnerability
being known to or exploited by a third party, before the release of the patch.</p>
<p>If the `AWS_LOCATION` setting was set, traversal was limited to that location only.
If all your files handling views (like form views) require authentication or special permission, the thread is limited to privileged users.</p>
<p>### Patches</p>
<p>The vulnerability has been fixed in version 5.5.1 and above.</p>
<p>### Workarounds</p>
<p>There is no feasible workaround. We must urge all users to immediately updated to a patched version.</p>
<p>### Detailed attack vector description</p>
<p>An attacker may use a request with malicious form data to traverse the entire AWS S3 bucket and perform destructive operations.</p>
<p>An attack could look as follows:
```bash
curl -X POST -F "s3file=file" -F "file=/priviliged/location/secrets.txt" https://www.example.com/any/path/will/work/
```</p>
<p>This will result in a request with files set and opened:</p>
<p>```python
&gt;&gt;&gt; request.FILES.getlist("file")
[File("/priviliged/location/secrets.txt")]
```</p>
<p>Since this behavior is injected via a middleware, any view can be called this way and will carry any files defined by the attacker.</p>
<p>Via the `s3file` form field, any input name can be specified, including multiple inputs. For each input, multiple files can be freely
picked of the S3 bucket.</p>
<p>#### Scenarios and their pra…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4w8f-hjm9-xwgf"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-24840</id>
    <title>gsd-2022-24840</title>
    <updated>2026-10-03T06:38:35.226912+00:00</updated>
    <content>gsd-2022-24840</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-24840"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2022-208</id>
    <title>PYSEC-2022-208</title>
    <updated>2026-10-03T06:38:35.226925+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: django-s3file</p>
<p>django-s3file is a lightweight file upload input for Django and Amazon S3 . In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the `AWS_LOCATION` setting was set, traversal was limited to that location only. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, prior to the release of the patch. The vulnerability has been fixed in version 5.5.1 and above. There is no feasible workaround. We must urge all users to immediately updated to a patched version.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2022-208"/>
  </entry>
</feed>
