# CVE-2026-25633: Statamic's missing authorization allows access to assets

> Authenticated users lacking asset permissions can download files and view metadata in Statamic CMS.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 11 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** GHSA-gwmx-9gcj-332h

## What is CVE-2026-25633?

CVE-2026-25633 is a medium-severity missing authorization vulnerability in statamic cms, published on 11 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Statamic is a, Laravel + Git powered CMS designed for building websites. Prior to 5.73.6 and 6.2.5, users without permission to view assets are able are able to download them and view their metadata. Logged-out users and users without permission to access the control panel are unable to take advantage of this. This has been fixed in 5.73.6 and 6.2.5.

Weakness: CWE-862 (Missing Authorization)

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

4 open source packages ship an affected version, including statamic/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 5.73.6 |
| `statamic/cms` | Packagist | All versions | 5.73.6 |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 | 6.2.5 |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 | 6.2.5 |

Products: Statamic Statamic.

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

Upgrade statamic/cms to a fixed version for your release line: 5.73.6 or 6.2.5.

## Is CVE-2026-25633 being exploited?

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

## Other vulnerabilities in statamic cms

- [CVE-2021-45364](https://insights.sbomify.com/CVE-2021-45364/): Code injection in n/a (critical 9.8)
- [CVE-2026-27593](https://insights.sbomify.com/CVE-2026-27593/): Statamic is vulnerable to account takeover via password reset link injection (critical 9.3)
- [CVE-2026-27939](https://insights.sbomify.com/CVE-2026-27939/): Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass (high 8.8)
- [CVE-2023-48217](https://insights.sbomify.com/CVE-2023-48217/): Remote code execution via form uploads in statamic/cms (high 8.8)
- [CVE-2017-11422](https://insights.sbomify.com/CVE-2017-11422/): Statamic framework Incorrect Permission Assignment (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25633 is a medium-severity missing authorization vulnerability in statamic cms, published on 11 Feb 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-25633 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 5.73.6
- statamic/cms (Packagist): affected all versions; fixed in 5.73.6
- statamic/cms (Packagist): affected from 6.0.0-alpha.1; fixed in 6.2.5
- statamic/cms (Packagist): affected from 6.0.0-alpha.1; fixed in 6.2.5

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-25633/ (Markdown: https://insights.sbomify.com/CVE-2026-25633/index.md)
```

## Sources

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

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