GHSA-6vjm-54vp-mxhx
HIGHJuju's unprivileged user running on charm node can leak any secret or relation data accessible to the local charm
Blast Radius
github.com/juju/juju🐹github.com/juju/juju🐹github.com/juju/juju🐹github.com/juju/juju🐹github.com/juju/jujuReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in Juju that resulted in the leak of the sensitive context ID, which allows a local unprivileged attacker to access other sensitive data or relation accessible to the local charm. A potential exploit where a user can run a bash loop attempting to execute hook tools. If running while another hook is executing, we log an error with the context ID, making it possible for the user to then use that ID in a following call successfully. This means an unprivileged user can access anything available via a hook tool such as config, relation data and secrets.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/juju/juju | all versions | 2.9.50 |
| 🐹Go | github.com/juju/juju | ≥ 3.0.0&&< 3.1.9 | 3.1.9 |
| 🐹Go | github.com/juju/juju | ≥ 3.2.0&&< 3.3.6 | 3.3.6 |
| 🐹Go | github.com/juju/juju | ≥ 3.4.0&&< 3.4.5 | 3.4.5 |
| 🐹Go | github.com/juju/juju | ≥ 3.5.0&&< 3.5.3 | 3.5.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/juju/juju. 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 github.com/juju/juju to 2.9.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vjm-54vp-mxhx 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-6vjm-54vp-mxhx 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-6vjm-54vp-mxhx. 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-6vjm-54vp-mxhx in your dependencies?
O3 detects GHSA-6vjm-54vp-mxhx across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.