GHSA-6VJM-54VP-MXHX

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.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

GHSA-6VJM-54VP-MXHX has a CVSS score of 8.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.50, 3.1.9, 3.3.6, 3.4.5, 3.5.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-6VJM-54VP-MXHX? GHSA-6VJM-54VP-MXHX is a high-severity improper privilege management vulnerability in github.com/juju/juju (go), affecting versions < 2.9.50. It is fixed in 2.9.50, 3.1.9, 3.3.6, 3.4.5, 3.5.3. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is GHSA-6VJM-54VP-MXHX? GHSA-6VJM-54VP-MXHX has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/juju/juju are affected by GHSA-6VJM-54VP-MXHX? github.com/juju/juju (go) versions < 2.9.50 is affected.
4. Is there a fix for GHSA-6VJM-54VP-MXHX? Yes. GHSA-6VJM-54VP-MXHX is fixed in 2.9.50, 3.1.9, 3.3.6, 3.4.5, 3.5.3. Upgrade to this version or later.
5. Is GHSA-6VJM-54VP-MXHX exploitable, and should I be worried? Whether GHSA-6VJM-54VP-MXHX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-6VJM-54VP-MXHX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-6VJM-54VP-MXHX?
   • Upgrade github.com/juju/juju to 2.9.50 or later
   • Upgrade github.com/juju/juju to 3.1.9 or later
   • Upgrade github.com/juju/juju to 3.3.6 or later
   • Upgrade github.com/juju/juju to 3.4.5 or later
   • Upgrade github.com/juju/juju to 3.5.3 or later