Improper Verification of Cryptographic Signature Affecting cephfs-top package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.18% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-CEPHFSTOP-18994928
  • published20 Aug 2026
  • disclosed19 Aug 2026

Introduced: 19 Aug 2026

NewCVE-2026-54330  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 cephfs-top.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cephfs-top package and not the cephfs-top package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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's signer intended and escalate their privileges. This issue is fixed in versions 20.2.4 and 19.2.6.

CVSS Base Scores

version 3.1