CVE-2026-32692 is a high-severity (CVSS 7.6) CWE-285 vulnerability in github.com/juju/juju. A fix is available for github.com/juju/juju — see the affected versions and patch details below.
Unauthorized update of out-of-scope Vault secrets
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2026-32692.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/juju/juju | ≥ 0.0.0-20230919230135-f6a66aa91eec&&< 0.0.0-20260319091847-d06919eb03ec | 0.0.0-20260319091847-d06919eb03ecgo get github.com/juju/juju@v0.0.0-20260319091847-d06919eb03ec |
Affected Products
jujucanonicalDetection & 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2026-32692 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.
Frequently Asked Questions
Is CVE-2026-32692 in your dependencies?
Find it across Go, including transitive dependencies.