<?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-10T18:27:13.926769+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-11136</id>
    <title>bdu:2026-11136</title>
    <updated>2026-10-10T18:27:13.929894+00:00</updated>
    <content>bdu:2026-11136</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-11136"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-seaweedfs-2026-54917</id>
    <title>BIT-seaweedfs-2026-54917 — SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access</title>
    <updated>2026-10-10T18:27:13.929927+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: seaweedfs</p>
<p>SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the S3 API gateway and the Iceberg REST catalog gateway construct their routers with mux.NewRouter().SkipClean(true). With path cleaning disabled, a .. segment inside the URL survives routing, so a request such as `GET /bucket-A/../evil-bucket/key`, is matched as bucket=bucket-A, object=../evil-bucket/key. The captured object key is then joined into a filer path with util.JoinPath (S3) / path.Join (Iceberg), which collapse the .. server-side, so the actual read or write lands in evil-bucket. This vulnerability is fixed in 4.30.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-seaweedfs-2026-54917"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-330387</id>
    <title>EUVD-2026-330387</title>
    <updated>2026-10-10T18:27:13.929961+00:00</updated>
    <content>EUVD-2026-330387</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-330387"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54917</id>
    <title>fkie_cve-2026-54917</title>
    <updated>2026-10-10T18:27:13.929975+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the S3 API gateway and the Iceberg REST catalog gateway construct their routers with mux.NewRouter().SkipClean(true). With path cleaning disabled, a .. segment inside the URL survives routing, so a request such as `GET /bucket-A/../evil-bucket/key`, is matched as bucket=bucket-A, object=../evil-bucket/key. The captured object key is then joined into a filer path with util.JoinPath (S3) / path.Join (Iceberg), which collapse the .. server-side, so the actual read or write lands in evil-bucket. This vulnerability is fixed in 4.30.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-54917"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-w62w-66v9-vvgv</id>
    <title>GHSA-w62w-66v9-vvgv — SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access</title>
    <updated>2026-10-10T18:27:13.929999+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/seaweedfs/seaweedfs</p>
<p>## Summary</p>
<p>The S3 API gateway and the Iceberg REST catalog gateway construct their routers with `mux.NewRouter().SkipClean(true)`. With path cleaning disabled, a `..` segment inside the URL survives routing, so a request such as:</p>
<p>```
GET /bucket-A/../evil-bucket/key
```</p>
<p>is matched as `bucket=bucket-A`, `object=../evil-bucket/key`. The captured object key is then joined into a filer path with `util.JoinPath` (S3) / `path.Join` (Iceberg), which collapse the `..` server-side, so the actual read or write lands in `evil-bucket`.</p>
<p>The captured path variables were never validated for traversal segments before reaching the handlers, so bucket isolation depended on downstream checks rather than on the path itself.</p>
<p>## Impact</p>
<p>- **With authentication disabled** (`enableAuth=false`): direct cross-bucket read and write. An object key containing `..` resolves to and operates on a different bucket than the one named in the request path.
- **With authentication enabled** (`enableAuth=true`): an authorization confused-deputy. IAM evaluates the policy against the mux `{bucket}` variable (`bucket-A`) in `iam.authRequestWithAuthType`, while the I/O is performed against the traversed target (`evil-bucket`). A principal authorized for one bucket can therefore reach objects in another bucket it has no grant for. This breaks tenant isolation.</p>
<p>The same class of traversal applies to the Iceberg REST catalog's `{prefix}`, `{namespace}`, and `{table}` path variables.</p>
<p>`%2e%2e`-encoded and `..\` (b…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-w62w-66v9-vvgv"/>
  </entry>
</feed>
