How severe is GHSA-hwj7-4vgc-j3v9?

No CVSS score has been assigned to GHSA-hwj7-4vgc-j3v9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hwj7-4vgc-j3v9?

GHSA-hwj7-4vgc-j3v9 affects the following packages: craftcms/aws-s3 (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-hwj7-4vgc-j3v9?

Update craftcms/aws-s3 to 2.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwj7-4vgc-j3v9 is resolved across your whole dependency graph.

How do I detect GHSA-hwj7-4vgc-j3v9 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/aws-s3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hwj7-4vgc-j3v9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hwj7-4vgc-j3v9?

O3 pinpoints whether GHSA-hwj7-4vgc-j3v9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hwj7-4vgc-j3v9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hwj7-4vgc-j3v9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hwj7-4vgc-j3v9?

GHSA-hwj7-4vgc-j3v9 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-hwj7-4vgc-j3v9 published, and has it been updated?

GHSA-hwj7-4vgc-j3v9 was published on March 16, 2026 and was last updated on March 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-hwj7-4vgc-j3v9

Amazon S3 for Craft CMS has an Information Disclosure vulnerability

Also known asCVE-2026-32265

Published

Mar 16, 2026

Updated

Mar 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk26th percentile+0.31%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘craftcms/aws-s3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/aws-s3`	≥ 2.0.2&&< 2.2.5	2.2.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/aws-s3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update craftcms/aws-s3 to 2.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwj7-4vgc-j3v9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hwj7-4vgc-j3v9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hwj7-4vgc-j3v9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-hwj7-4vgc-j3v9 in your dependencies?

O3 detects GHSA-hwj7-4vgc-j3v9 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works