CVE Catalog

CVE-2026-42882

CriticalCVSS 9.4
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.55%

46th percentile - higher than 46% of all known CVEs

Summary

Prior to 5.0.0, oxyno-zeta/s3-proxy contains an authentication bypass caused by inconsistent URL path interpretation between the authentication middleware and the bucket handler. The middleware evaluates patterns against the percent-encoded request URI while the bucket handler builds S3 object keys from the decoded path, and combined with glob matching across path separators this allows unauthenticated attackers to read, write, or delete objects in protected S3 namespaces.

Risk Assessment

An unauthenticated attacker with network access can perform PUT, GET, and DELETE operations on objects in authentication-protected S3 namespaces, risking data exposure, modification, or loss.

Recommendation

Update s3-proxy to version 5.0.0 or later, which fixes this vulnerability.

Related vulnerabilities

Original NVD description (English source)

oxyno-zeta/s3-proxy is an aws s3 proxy written in go. Prior to 5.0.0, s3-proxy contains an authentication bypass caused by inconsistent URL path interpretation between the authentication middleware and the bucket handler. The authentication middleware evaluates resource path patterns against the percent-encoded request URI (r.URL.RequestURI()), while the bucket handler constructs S3 object keys from the decoded path (r.URL.Path). This mismatch, combined with the glob library being invoked without a path separator (causing * to match across / boundaries), allows unauthenticated attackers to write to, read from, or delete objects in protected S3 namespaces. Exploitation is possible via three techniques: (1) using * patterns that match across path separators to reach protected routes via path traversal (e.g., /open/foo/drafts/../restricted/), (2) using percent-encoded slashes (%2F) to collapse multiple path segments into a single token at the auth layer while the decoded form resolves to a protected namespace at the storage layer, and (3) using dot-dot segments (../) under ** prefix patterns, where the raw path matches an open route while Go's URL parser resolves the traversal to a protected path before the bucket handler runs. An unauthenticated attacker with network access can perform unauthorized PUT, GET, or DELETE operations on objects in authentication-protected S3 namespaces. This vulnerability is fixed in 5.0.0.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS