Authentication Bypass in Alluxio S3 REST Proxy
Alluxio versions 2.9.5 and earlier contain a critical authentication vulnerability that allows unauthenticated attackers to spoof identity and perform unauthorized operations by failing to verify AWS Signature Version 4 requests.
CVE search metadata
CVE search record: CVE-2026-79787. Severity: critical. CVSS: 9.8. KEV: no. Product: alluxio. Brief: Authentication Bypass in Alluxio S3 REST Proxy. Brief link: https://feed.craftedsignal.io/briefs/2026-08-alluxio-s3-auth-bypass/
Alluxio's S3 REST proxy, used in versions 2.9.5 and earlier, is vulnerable to an authentication bypass due to a failure to verify AWS Signature Version 4 (SigV4) signatures in its default configuration. This flaw allows unauthenticated remote attackers to impersonate any user or service account by manipulating the Authorization header. Because the proxy does not validate the integrity or authenticity of the provided credentials, attackers can supply arbitrary usernames to gain unauthorized access to the underlying storage resources. This allows for full read, write, and delete operations on data managed by Alluxio. Given that this component is often used in data platform architectures, the impact of unauthorized data manipulation or exfiltration is severe. Organizations should prioritize updating Alluxio instances to the recommended patched versions once available to prevent unauthorized access.
Attack Chain
- Attacker performs reconnaissance on the Alluxio deployment to identify the S3 REST proxy endpoint.
- Attacker crafts an HTTP request to the target S3 proxy endpoint.
- Attacker inserts a malformed or arbitrary "Authorization" header containing a target username into the request.
- The Alluxio S3 REST proxy receives the request and parses the Authorization header.
- The proxy fails to cryptographically verify the signature associated with the provided identity.
- The proxy incorrectly authenticates the request based solely on the user-provided identity in the header.
- The proxy executes the requested data operation (read, write, or delete) with the permissions of the impersonated user.
- The final objective is reached: unauthorized access, modification, or exfiltration of sensitive data stored within the Alluxio system.
Impact
Successful exploitation allows unauthenticated remote attackers to gain full administrative control over data managed by the S3 REST proxy. This includes reading sensitive datasets, overwriting or corrupting existing data, and deleting critical information. The vulnerability affects all Alluxio deployments using the default S3 REST proxy configuration up to and including version 2.9.5.
Recommendation
- Audit all Alluxio deployments to confirm version usage; upgrade to a patched version immediately upon release (CVE-2026-79787).
- Implement strict network access control lists (ACLs) to restrict access to the Alluxio S3 REST proxy endpoint to trusted internal networks only.
- Enable verbose access logging for the S3 REST proxy and alert on any requests containing suspicious or non-standard Authorization headers, as the application logic currently fails to validate them.
- Deploy the Sigma rules in this brief to monitor for unauthorized requests targeting the S3 proxy endpoint (see rule below).
Immediate actions
Review Alluxio footprint and identify instances using S3 REST proxy
Mitigations
Patch Alluxio to latest version
CVE-2026-79787
Detection coverage 1
Detects CVE-2026-79787 Exploitation - Alluxio S3 Authentication Bypass Attempt
highDetects potential exploitation attempts of CVE-2026-79787 where unauthorized or unverified Authorization headers are sent to the Alluxio S3 REST proxy.
Detection queries are available on the platform. Get full rules →