CVE-2026-32691 — Incorrect Ownership Assignment in Juju

CWE-708 — Incorrect Ownership Assignment6 documents5 sources
Severity
5.3MEDIUMNVD
EPSS
0.0%
top 98.47%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
2
Canonical JujuGithub.com Juju Juju
Timeline
PublishedMar 18
Latest updateMar 23

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.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitability: 1.6 | Impact: 3.6

Affected Packages3 packages

▶CVEListV5canonical/juju3.0.0 — 3.6.19
▶NVDcanonical/juju3.0.0 — 3.6.19
▶Gogithub.com/juju_juju3.0.0 — 3.6.19

🔴Vulnerability Details

4
OSV
Juju affected by timing ownership claim attack on new external back-end secrets in github.com/juju/juju↗2026-03-23
▶
GHSA
Juju affected by timing ownership claim attack on new external back-end secrets↗2026-03-19
▶
OSV
Juju affected by timing ownership claim attack on new external back-end secrets↗2026-03-19
▶
CVEList
Timing ownership claim attack on new external back-end secrets↗2026-03-18
▶

🕵️Threat Intelligence

1
Wiz
CVE-2026-32691 Impact, Exploitability, and Mitigation Steps | Wiz↗
▶
CVE-2026-32691 — Incorrect Ownership Assignment in Juju | cvebase