# CVE-2026-32693: Unauthorized access to Kubernetes secrets in Juju

> Attackers can bypass authorization checks to read or modify Kubernetes secrets in Juju, compromising sensitive data integrity and confidentiality.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-439w-v2p7-pggc, GO-2026-4777

## What is CVE-2026-32693?

CVE-2026-32693 is a high-severity missing authorization vulnerability in Canonical Juju, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Juju from version 3.0.0 through 3.6.18, the authorization of the "secret-set" tool is not performed correctly, which allows a grantee to update the secret content, and can lead to reading or updating other secrets. When the "secret-set" tool logs an error in an exploitation attempt, the secret is still updated contrary to expectations, and the new value is visible to both the owner and the grantee.

Weakness: CWE-863 (Incorrect Authorization), CWE-778 (Insufficient Logging), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-32693?

3 open source packages ship an affected version, including github.com/juju/juju. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/juju/juju` | Go | From 0.0.0-20221021155847-35c560704ee2 | 0.0.0-20260319091847-d06919eb03ec |
| `github.com/juju/juju` | Go | From 0.0.0-20221021155847-35c560704ee2 | 0.0.0-20260319091847-d06919eb03ec |
| `github.com/juju/juju` | Go | From 0.0.0-20221021155847-35c560704ee2 | 0.0.0-20260319091847-d06919eb03ec |

Products: Canonical Juju.

## How do I fix CVE-2026-32693?

Upgrade github.com/juju/juju to 0.0.0-20260319091847-d06919eb03ec or later.

## Is CVE-2026-32693 being exploited?

There is no known exploitation of CVE-2026-32693 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Juju

- [CVE-2026-4370](https://insights.sbomify.com/CVE-2026-4370/): Improper TLS Client/Server authentication and certificate verification on Database Cluster (critical 10.0)
- [CVE-2026-5412](https://insights.sbomify.com/CVE-2026-5412/): Juju CloudSpec API could leak senstive information (critical 9.9)
- [CVE-2017-9232](https://insights.sbomify.com/CVE-2017-9232/): Juju uses a UNIX domain socket without setting appropriate permissions (critical 9.8)
- [CVE-2025-0928](https://insights.sbomify.com/CVE-2025-0928/): Arbitrary executable upload via authenticated endpoint (high 8.8)
- [CVE-2025-53513](https://insights.sbomify.com/CVE-2025-53513/): Zip slip vulnerability in Juju (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32693 and fix it if it is affected.

What it is: CVE-2026-32693 is a high-severity missing authorization vulnerability in Canonical Juju, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32693 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/juju/juju (Go): affected from 0.0.0-20221021155847-35c560704ee2; fixed in 0.0.0-20260319091847-d06919eb03ec
- github.com/juju/juju (Go): affected from 0.0.0-20221021155847-35c560704ee2; fixed in 0.0.0-20260319091847-d06919eb03ec
- github.com/juju/juju (Go): affected from 0.0.0-20221021155847-35c560704ee2; fixed in 0.0.0-20260319091847-d06919eb03ec

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32693/ (Markdown: https://insights.sbomify.com/CVE-2026-32693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32693
- OSV: https://osv.dev/vulnerability/CVE-2026-32693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32693/
Summaries are generated and may contain mistakes; the official description above is the record.