https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 23:33:05 +0000 https://vulnerability.circl.lu/vuln/bit-ceph-2026-54330 <p><strong>Affected:</strong> Bitnami: ceph</p> <p>Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Ceph Object Gateway (RGW) SigV4 handler does not reject requests that carry x-amz-* headers absent from the signed header set, allowing anyone holding a presigned URL to attach arbitrary unsigned x-amz-* headers that RGW will honor. AWS S3 requires every x-amz-* header on a SigV4 request to be signed and rejects requests bearing additional unsigned headers, but RGW validates only the headers listed in X-Amz-SignedHeaders and ignores any extra ones, so they take effect without being covered by the signature. By adding such headers to a presigned PUT URL, an attacker can grant themselves more capabilities than the URL&#39;s signer intended and escalate their privileges. This issue is fixed in versions 20.2.4 and 19.2.6.</p> <p><strong>Affected:</strong> Bitnami: ceph</p> <p>Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Ceph Object Gateway (RGW) SigV4 handler does not reject requests that carry x-amz-* headers absent from the signed header set, allowing anyone holding a presigned URL to attach arbitrary unsigned x-amz-* headers that RGW will honor. AWS S3 requires every x-amz-* header on a SigV4 request to be signed and rejects requests bearing additional unsigned headers, but RGW validates only the headers listed in X-Amz-SignedHeaders and ignores any extra ones, so they take effect without being covered by the signature. By adding such headers to a presigned PUT URL, an attacker can grant themselves more capabilities than the URL&#39;s signer intended and escalate their privileges. This issue is fixed in versions 20.2.4 and 19.2.6.</p> https://vulnerability.circl.lu/vuln/bit-ceph-2026-54330 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1057 certfr-2026-avi-1057 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1057 https://vulnerability.circl.lu/vuln/fkie_cve-2026-54330 <p>Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Ceph Object Gateway (RGW) SigV4 handler does not reject requests that carry x-amz-* headers absent from the signed header set, allowing anyone holding a presigned URL to attach arbitrary unsigned x-amz-* headers that RGW will honor. AWS S3 requires every x-amz-* header on a SigV4 request to be signed and rejects requests bearing additional unsigned headers, but RGW validates only the headers listed in X-Amz-SignedHeaders and ignores any extra ones, so they take effect without being covered by the signature. By adding such headers to a presigned PUT URL, an attacker can grant themselves more capabilities than the URL&#39;s signer intended and escalate their privileges. This issue is fixed in versions 20.2.4 and 19.2.6.</p> <p>Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Ceph Object Gateway (RGW) SigV4 handler does not reject requests that carry x-amz-* headers absent from the signed header set, allowing anyone holding a presigned URL to attach arbitrary unsigned x-amz-* headers that RGW will honor. AWS S3 requires every x-amz-* header on a SigV4 request to be signed and rejects requests bearing additional unsigned headers, but RGW validates only the headers listed in X-Amz-SignedHeaders and ignores any extra ones, so they take effect without being covered by the signature. By adding such headers to a presigned PUT URL, an attacker can grant themselves more capabilities than the URL&#39;s signer intended and escalate their privileges. This issue is fixed in versions 20.2.4 and 19.2.6.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-54330 https://vulnerability.circl.lu/vuln/msrc_cve-2026-54330 msrc_CVE-2026-54330 https://vulnerability.circl.lu/vuln/msrc_cve-2026-54330 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-54330 <p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: ceph, Ubuntu:Pro:20.04:LTS: ceph, Ubuntu:22.04:LTS: ceph, Ubuntu:24.04:LTS: ceph, Ubuntu:26.04:LTS: ceph</p> <p>Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Ceph Object Gateway (RGW) SigV4 handler does not reject requests that carry x-amz-* headers absent from the signed header set, allowing anyone holding a presigned URL to attach arbitrary unsigned x-amz-* headers that RGW will honor. AWS S3 requires every x-amz-* header on a SigV4 request to be signed and rejects requests bearing additional unsigned headers, but RGW validates only the headers listed in X-Amz-SignedHeaders and ignores any extra ones, so they take effect without being covered by the signature. By adding such headers to a presigned PUT URL, an attacker can grant themselves more capabilities than the URL&#39;s signer intended and escalate their privileges. This issue is fixed in versions 20.2.4 and 19.2.6.</p> <p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: ceph, Ubuntu:Pro:20.04:LTS: ceph, Ubuntu:22.04:LTS: ceph, Ubuntu:24.04:LTS: ceph, Ubuntu:26.04:LTS: ceph</p> <p>Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the Ceph Object Gateway (RGW) SigV4 handler does not reject requests that carry x-amz-* headers absent from the signed header set, allowing anyone holding a presigned URL to attach arbitrary unsigned x-amz-* headers that RGW will honor. AWS S3 requires every x-amz-* header on a SigV4 request to be signed and rejects requests bearing additional unsigned headers, but RGW validates only the headers listed in X-Amz-SignedHeaders and ignores any extra ones, so they take effect without being covered by the signature. By adding such headers to a presigned PUT URL, an attacker can grant themselves more capabilities than the URL&#39;s signer intended and escalate their privileges. This issue is fixed in versions 20.2.4 and 19.2.6.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-54330