CVE-2026-44692: Authenticated Sharp users can download unrelated Laravel Storage objects through the generic download endpoint
Sharp exposes a generic download endpoint that authorizes access only to the supplied Sharp entity instance, but then reads the target storage disk and path from request parameters. Because the requested storage object is not bound to the authorized entity instance, an authenticated Sharp user who can view one valid record may use that record as an authorization anchor to download unrelated disk-relative objects…
Published May 15, 2026 · Updated Jun 11, 2026
Affected packages
code16/sharp
- Ecosystem
- Composer (PHP)
- Affected
- < 9.22.0
- Fixed in
- 9.22.0
- Check
composer show code16/sharp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Sharp exposes a generic download endpoint that authorizes access only to the supplied Sharp entity instance, but then reads the target storage disk and path from request parameters.
Because the requested storage object is not bound to the authorized entity instance, an authenticated Sharp user who can view one valid record may use that record as an authorization anchor to download unrelated disk-relative objects from configured Laravel Storage disks.
The confirmed impact is authenticated disclosure of unrelated objects from configured Laravel Storage disks. This issue does not imply arbitrary host filesystem access outside configured Laravel Storage disk roots.
Impact
An authenticated Sharp user with view access to at least one valid Sharp entity instance may be able to download unrelated files from configured Laravel Storage disks by supplying a different disk and path to the generic download endpoint.
Depending on the application, exposed files may include exports, backups, invoices, internal documents, uploads belonging to other records, tenant-specific data, or operational files stored on private application disks.
The attacker does not need authorization to the storage object being downloaded. They only need an authenticated Sharp session and view access to one valid entity instance that can be used as the authorization anchor.
Attack requirements
An attacker must have:
- an authenticated Sharp session
- view access to at least one valid Sharp entity instance
The attacker does not need authorization to the storage object being downloaded.
Affected endpoint
GET /sharp/{globalFilter}/download/{entityKey}/{instanceId?}
Patches
After the fix, requests to the generic download endpoint without a valid signature are rejected. Modifying the disk, path, entityKey, or instanceId parameters of a Sharp-generated download URL invalidates the signature and prevents the modified request from being used to download another storage object.
Workarounds
If upgrading is not immediately possible, applications should restrict downloads.allowed_disks to the smallest possible set of disks required by Sharp downloads.
Applications should also avoid storing sensitive unrelated files on disks reachable by Sharp’s generic download endpoint, and should add application-level controls to ensure that requested files are bound to the authorized record.
Disk allowlisting reduces the reachable storage surface, but it does not fully fix the missing per-record file binding. Upgrading to a patched version is recommended.
Resources
- Laravel signed URLs documentation: https://laravel.com/docs/urls#signed-urls
- CWE-639: https://cwe.mitre.org/data/definitions/639.html
Credited to baradika.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-84974
code16/sharp: Arbitrary class instantiation through the embed_key API parameter
medium5.4Nov 12, 2026CVE-2026-84987
code16/sharp: Server-side request forgery through an unanchored autocomplete endpoint check
medium5.4Nov 12, 2026CVE-2026-61823
code16 Sharp vulnerable to stored XSS via iframe srcdoc Attribute
high7.3Sep 25, 2026CVE-2026-61825
code16/sharp has a stored XSS via data-html-content Sanitizer Bypass
high8.7Sep 25, 2026CVE-2026-53634
Sharp Missing Authorization Check in Quick Creation Command Endpoints
medium4.3Jul 8, 2026CVE-2026-33686
Sharp is Vulnerable to Path Traversal via Unsanitized Extension in FileUtil
high8.8Mar 25, 2026
