/

CVE-2026-57855

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-284) in Cockpit Bucket API

CVE-2026-57855

Deferred

Vulnerability type

Category:

Missing Authorization / Broken Access Control

CWE:

CWE-284

Impact:

Privilege Escalation and Unauthorized Data Manipulation

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Cockpit CMS exposes a missing authorization flaw in its Bucket file storage API, allowing bucket operations without proper access control checks.

Any authenticated user, regardless of role, can execute administrative file commands on any bucket, creating a high risk for data exposure and tampering in multi-user environments.

Affected context

The vulnerability arises in Cockpit CMS deployments that use the Bucket file storage API at /system/buckets/api for managing files and folders.

It is most relevant in multi-user setups where buckets are intended to be segregated by roles (e.g., admin-only buckets versus standard user buckets).

When any authenticated CMS account can reach the Bucket API, the lack of authorization checks means role restrictions are effectively bypassed, even if higher-level UI or configuration implies stricter access.

Exploit preconditions

  • Attack surface: HTTP requests to the Cockpit CMS Bucket API endpoint /system/buckets/api.
  • Required access: Any valid authenticated Cockpit CMS account; no elevated role or admin permissions are needed.
  • Trigger point: Invoking the api() method in modules/System/Controller/Buckets.php with commands such as ls, upload, removefiles, rename, and createfolder against arbitrary bucket names.
  • Why exploitation is possible: The API handler executes bucket commands without enforcing ACL or role-based authorization checks, so the system trusts any authenticated caller for all bucket operations on all buckets.

Why this happens

The underlying bug is a missing authorization check on a sensitive backend API responsible for file and folder management in Cockpit CMS.

While authentication is required, the api() method in modules/System/Controller/Buckets.php does not validate whether the caller is permitted to act on a given bucket or perform specific commands.

This maps directly to CWE-284: Improper Access Control, where an application fails to apply role, ACL, or resource-level authorization controls after authentication, leaving privileged operations exposed to ordinary users.

Potential impact

  • Authenticated users may upload arbitrary files into admin-only or sensitive buckets.
  • Authenticated users could delete or remove files from storage buckets, causing data loss.
  • Authenticated users can rename or reorganize content, leading to content disruption or defacement.
  • Authenticated users could list directory contents in restricted buckets, exposing internal or confidential data.
  • Authenticated users may create new folders in privileged buckets, facilitating further misuse or staging of malicious files.

General mitigation guidance

Effective mitigation focuses on enforcing robust authorization checks on all file storage operations, not just front-end views.

Recommended defensive patterns include:

  • Applying role-based access control (RBAC) or ACL enforcement within the Bucket API layer so each command validates the caller's permissions for the target bucket.
  • Centralizing authorization logic for resource operations to avoid ad-hoc checks and reduce the chance of forgotten validation.
  • Restricting generic "any authenticated user" access to sensitive APIs and aligning endpoint exposure with least-privilege principles.
  • Treating buckets as protected resources with explicit ownership or role bindings, ensuring the system denies operations when no explicit permission is granted.

How teams detect issues like this

Detection typically involves a combination of code analysis and runtime monitoring:

  • Static analysis or manual code review to identify controller methods and APIs that perform state-changing operations without accompanying authorization checks.
  • Reviewing access control middleware usage to ensure all sensitive routes (like /system/buckets/api) are covered by consistent authorization policies, not just authentication.
  • Implementing logging for bucket operations (upload, remove, rename, list) and analyzing logs for unusual activity by low-privilege accounts.
  • Employing automated security testing tools that probe APIs for role bypass and broken access control, validating that role-restricted resources cannot be modified by standard users.

Sources

SourceLink
gist.github.comgist.github.com/sermikr0/821c4edd3c34e98a62a50b07707785bd
github.comgithub.com/Cockpit-HQ/Cockpit/commit/dde2d1d74f5f4e11de42a298918ea8c9684f932c
github.comgithub.com/cockpit-hq/cockpit
vulncheck.comvulncheck.com/advisories/cockpit-cms-missing-authorization-in-bucket-file-storage-api

Frequently asked

questions

Yes. Any authenticated Cockpit CMS user, even with minimal privileges, can perform all bucket operations on any bucket because the API does not enforce role or ACL checks.

No. Administrative credentials are not required; a standard user account with access to the CMS and the Bucket API endpoint is sufficient to abuse the flaw.

The most robust fix is to enforce strict authorization at the Bucket API level, ensuring each operation checks the caller's role, permissions, and relationship to the target bucket before execution, using centralized RBAC or ACL mechanisms.

Design APIs so that every sensitive operation passes through a consistent authorization layer, adopt least-privilege defaults, and include access control checks as a mandatory review item in code review and automated security testing pipelines.

Find out what's already
exploitable in your codebase.