GHSA-2ccp-vqmv-4r4x — s3proxy
Fix: apache/jclouds@b0819e0GHSA-2ccp-vqmv-4r4x is a Path Traversal vulnerability in org.gaul:s3proxy. A fix is available for org.gaul:s3proxy — see the affected versions and patch details below.
S3Proxy allows insecure path traversal in filesystem and filesystem-nio2 storage backends
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2ccp-vqmv-4r4x.
EPSS Exploitation Probability
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.
Real-World Exposure
org.gaul:s3proxyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Users of the filesystem and filesystem-nio2 storage backends could unintentionally expose local files to authenticated clients.
Patches
Upgrade to S3Proxy 2.6.0 which includes apache/jclouds@b0819e0ef5e08c792a4d1724b938714ce9503aa3 and 86b6ee4749aa163a78e7898efc063617ed171980.
Workarounds
None
References
Privately reported by XBOW Team @xbow-security.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.gaul:s3proxy | all versions | 2.6.0org.gaul:s3proxy:2.6.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.gaul:s3proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.gaul:s3proxy to 2.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2ccp-vqmv-4r4x 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2ccp-vqmv-4r4x can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2ccp-vqmv-4r4x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2ccp-vqmv-4r4x in your dependencies?
O3 Security finds GHSA-2ccp-vqmv-4r4x across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.