# CVE-2026-44692: Authenticated Sharp users can download unrelated Laravel Storage objects through the generic download endpoint

> Authenticated users can download unrelated storage objects by manipulating request parameters, leading to unauthorized data disclosure.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-748w-hm6r-qc7v

## What is CVE-2026-44692?

CVE-2026-44692 is a high-severity missing authorization vulnerability in code16 sharp, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sharp is a content management framework built for Laravel as a package. Prior to version 9.22.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. This issue has been patched in version 9.22.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-44692?

2 open source packages ship an affected version, including code16/sharp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code16/sharp` | Packagist | All versions | 9.22.0 |
| `code16/sharp` | Packagist | All versions | 9.22.0 |

## How do I fix CVE-2026-44692?

Upgrade code16/sharp to 9.22.0 or later.

## Is CVE-2026-44692 being exploited?

There is no known exploitation of CVE-2026-44692 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44692 and fix it if it is affected.

What it is: CVE-2026-44692 is a high-severity missing authorization vulnerability in code16 sharp, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44692 in the wild and no public exploit code.

Affected packages and fixed versions:
- code16/sharp (Packagist): affected all versions; fixed in 9.22.0
- code16/sharp (Packagist): affected all versions; fixed in 9.22.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44692/ (Markdown: https://insights.sbomify.com/CVE-2026-44692/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44692
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44692
- OSV: https://osv.dev/vulnerability/CVE-2026-44692

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44692/
Summaries are generated and may contain mistakes; the official description above is the record.