# CVE-2026-32265: Amazon S3 for Craft CMS has an Information Disclosure vulnerability

> Unauthenticated users can view a list of accessible Amazon S3 buckets via an exposed endpoint in the Craft CMS plugin.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-hwj7-4vgc-j3v9

## What is CVE-2026-32265?

CVE-2026-32265 is a medium-severity vulnerability in craftcms aws-s3, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Amazon S3 for Craft CMS plugin provides an Amazon S3 integration for Craft CMS. In versions 2.0.2 through 2.2.4, unauthenticated users can view a list of buckets the plugin has access to. The `BucketsController->actionLoadBucketData()` endpoint allows unauthenticated users with a valid CSRF token to view a list of buckets that the plugin is allowed to see. Users should update to version 2.2.5 of the plugin to mitigate the issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including craftcms/aws-s3.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/aws-s3` | Packagist | From 2.0.2 | 2.2.5 |
| `craftcms/aws-s3` | Packagist | From 2.0.2 | 2.2.5 |

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

Upgrade craftcms/aws-s3 to 2.2.5 or later.

## Is CVE-2026-32265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32265 is a medium-severity vulnerability in craftcms aws-s3, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32265 in the wild and no public exploit code.

Affected packages and fixed versions:
- craftcms/aws-s3 (Packagist): affected from 2.0.2; fixed in 2.2.5
- craftcms/aws-s3 (Packagist): affected from 2.0.2; fixed in 2.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-32265/ (Markdown: https://insights.sbomify.com/CVE-2026-32265/index.md)
```

## Sources

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

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