How severe is GHSA-89x7-5m5m-mcmm?

GHSA-89x7-5m5m-mcmm has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-89x7-5m5m-mcmm?

GHSA-89x7-5m5m-mcmm affects the following packages: github.com/juju/juju (Go). Ecosystems affected: Go.

How do I fix GHSA-89x7-5m5m-mcmm?

Update github.com/juju/juju to 0.0.0-20260319091847-d06919eb03ec or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-89x7-5m5m-mcmm is resolved across your whole dependency graph.

How do I detect GHSA-89x7-5m5m-mcmm in my Go dependencies?

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.

How do I mitigate GHSA-89x7-5m5m-mcmm 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-89x7-5m5m-mcmm?

O3 pinpoints whether GHSA-89x7-5m5m-mcmm 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-89x7-5m5m-mcmm actively exploited in the wild?

No public exploit code has been indexed for GHSA-89x7-5m5m-mcmm 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 type of vulnerability is GHSA-89x7-5m5m-mcmm?

GHSA-89x7-5m5m-mcmm is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-89x7-5m5m-mcmm published, and has it been updated?

GHSA-89x7-5m5m-mcmm was published on March 19, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-89x7-5m5m-mcmm: Juju has unauthorized update of out-of-sco…

Blast Radius

1 pkg affected

🐹github.com/juju/juju

Real-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 authorization bypass vulnerability in the Vault secrets back-end implementation of Juju versions 3.1.6 through 3.6.18 allows an authenticated unit agent to perform unauthorized updates to secret revisions. With sufficient information, an attacker can poison any existing secret revision within the scope of that Vault secret back-end.

Impact

An authenticated unit agent can update any secret revision of a Vault back-end that the unit's model uses. With sufficient information, an attacker can poison any existing secret revision within the scope of that Vault secret back-end.

Patches

3.6.19

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/juju/juju`	≥ 0.0.0-20230919230135-f6a66aa91eec&&< 0.0.0-20260319091847-d06919eb03ec	0.0.0-20260319091847-d06919eb03ec

Detection & mitigation playbook

Open-source dependency

Detect
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 0.0.0-20260319091847-d06919eb03ec or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-89x7-5m5m-mcmm 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-89x7-5m5m-mcmm 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-89x7-5m5m-mcmm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An authorization bypass vulnerability in the Vault secrets back-end implementation of Juju versions 3.1.6 through 3.6.18 allows an authenticated unit agent to perform unauthorized updates to secret revisions. With sufficient information, an attacker can poison any existing secret revision within the scope of that Vault secret back-end. ### Impact An authenticated unit agent can update any secret revision of a Vault back-end that the unit's model uses. With sufficient information, an attacker can poison any existing secret revision within the scope of that Vault secret back-end. ### Patches

O3 Security · Impact-Aware SCA

Is GHSA-89x7-5m5m-mcmm in your dependencies?

O3 detects GHSA-89x7-5m5m-mcmm across Go 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

GHSA-89x7-5m5m-mcmm