Skip to main content
Vulnerability Database/CVE-2026-111332

CVE-2026-111332: OxiCloud Authorization Bypass Vulnerability

CVE-2026-111332 is an authorization bypass flaw in OxiCloud versions 0.9.1 through 0.9.3 that lets attackers access password-protected shares using cached cookies. This article covers the technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111332 Overview

OxiCloud versions 0.9.1 through 0.9.3 contain an incorrect authorization vulnerability [CWE-863] in the share access control logic. When an administrator adds password protection to a previously public share, the application fails to revoke access for anonymous visitors who already hold a valid oxi_shares share-ring cookie. Attackers retain the ability to read shared files and folder contents by issuing authenticated GET /api/files/{id} requests, bypassing the newly applied password gate. The flaw affects the self-hosted OxiCloud file storage platform maintained by AtalayaLabs.

Critical Impact

Anonymous users with pre-existing share-ring cookies retain read access to shared files after password protection is applied, defeating the intended access control change.

Affected Products

  • OxiCloud 0.9.1
  • OxiCloud 0.9.2
  • OxiCloud 0.9.3

Discovery Timeline

  • 2026-10-15 - CVE-2026-111332 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111332

Vulnerability Analysis

The vulnerability resides in the OxiCloud share service, specifically in how share grants are tracked and revoked. OxiCloud issues an oxi_shares cookie containing a share-ring identifier when an anonymous visitor accesses a public share. The share-ring acts as a persistent grant table that authorizes subsequent API calls to GET /api/files/{id} for the shared resource.

When an administrator adds password protection to a share, the application updates the share's password requirement but does not invalidate existing entries in the share-ring. The authorization check continues to honor the cached grant, treating prior cookie holders as already-authenticated for the share. See the HackMD OxiCloud Password Grant Analysis for a full walkthrough.

Root Cause

The root cause is a missing revocation step in the password-grant workflow. Code paths in share_service.rs and share_ring.rs update share metadata without purging previously issued share-ring entries. This is a classic incorrect authorization pattern where a state change on the resource is not propagated to cached access decisions.

Attack Vector

An attacker must first obtain a valid oxi_shares cookie by accessing the share while it is still public. After the owner enables password protection, the attacker replays the cookie against GET /api/files/{id} and continues to receive shared file content. Exploitation requires no authentication, no user interaction, and only network access to the OxiCloud instance. Refer to the VulnCheck OxiCloud Advisory for the vendor-independent writeup.

// No verified exploit code is published. See the HackMD analysis for a request-level description.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-111332

Indicators of Compromise

  • Requests to GET /api/files/{id} carrying an oxi_shares cookie that targets a share which has transitioned from public to password-protected.
  • Access to shared files from client IPs that never submitted the share password after protection was enabled.
  • Repeated reads from a single oxi_shares share-ring identifier across long time windows.

Detection Strategies

  • Correlate share-password-change audit events with subsequent successful /api/files/{id} reads that reference the same share identifier without a password submission event.
  • Baseline the lifecycle of oxi_shares cookies and alert on grants that persist across share state changes.
  • Review OxiCloud application logs for anonymous reads occurring after an administrative password-protection action on the same share.

Monitoring Recommendations

  • Enable verbose logging on the OxiCloud share service and forward logs to a centralized analytics platform for retention and correlation.
  • Monitor outbound data volumes from /api/files/ endpoints for anomalous spikes tied to shares that were recently restricted.
  • Track administrative actions on shares as high-signal events and link them to downstream access decisions.

How to Mitigate CVE-2026-111332

Immediate Actions Required

  • Inventory all OxiCloud deployments and identify instances running 0.9.1, 0.9.2, or 0.9.3.
  • Rotate or invalidate the server-side share-ring state so all existing oxi_shares cookies are forced to re-authenticate against current share settings.
  • Delete and recreate any share that transitioned from public to password-protected while running an affected version.

Patch Information

No fixed version is listed in the published advisory references at the time of writing. Track the GitHub OxiCloud Repository and the VulnCheck OxiCloud Advisory for an upstream fix that revokes share-ring grants on password changes.

Workarounds

  • Restrict network exposure of OxiCloud instances using firewall rules or a reverse proxy that enforces authentication before reaching /api/files/.
  • Instead of adding password protection to an existing public share, delete the share and create a new password-protected share with a new identifier.
  • Clear persistent share-ring state at the storage layer after making any share more restrictive.
bash
# Example: block anonymous access to the OxiCloud files API at a reverse proxy
# until a patched version is deployed
location /api/files/ {
    auth_request /internal/validate-session;
    proxy_pass http://oxicloud_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.