# CVE-2026-32691: Timing ownership claim attack on new external back-end secrets

> An authenticated unit agent can exploit a race condition to claim ownership of new secrets and read their initial content.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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-gfgr-6hrj-85ww, GO-2026-4769

## What is CVE-2026-32691?

CVE-2026-32691 is a medium-severity 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

A race condition in the secrets management subsystem of Juju versions 3.0.0 through 3.6.18 allows an authenticated unit agent to claim ownership of a newly initialized secret. Between generating a Juju Secret ID and creating the secret's first revision, an attacker authenticated as another unit agent can claim ownership of a known secret. This leads to the attacking unit being able to read the content of the initial secret revision.

Weakness: CWE-708 (Incorrect Ownership Assignment)

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

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 | All versions | None |
| `github.com/juju/juju` | Go | From 3.0.0 | 3.6.19 |
| `github.com/juju/juju` | Go | From 3.0.0 | 3.6.19 |

Products: Canonical Juju.

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

Upgrade github.com/juju/juju to 3.6.19 or later.

## Is CVE-2026-32691 being exploited?

There is no known exploitation of CVE-2026-32691 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-2026-32693](https://insights.sbomify.com/CVE-2026-32693/): Unauthorized access to Kubernetes secrets in Juju (high 8.8)
- [CVE-2025-0928](https://insights.sbomify.com/CVE-2025-0928/): Arbitrary executable upload via authenticated endpoint (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32691 is a medium-severity 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-32691 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/juju/juju (Go): affected all versions; no fix listed
- github.com/juju/juju (Go): affected from 3.0.0; fixed in 3.6.19
- github.com/juju/juju (Go): affected from 3.0.0; fixed in 3.6.19

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-32691/ (Markdown: https://insights.sbomify.com/CVE-2026-32691/index.md)
```

## Sources

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

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