CVE-2026-32691
Canonical Juju 3.0.0 – 3.6.19
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-32691 is a medium-severity Incorrect Ownership Assignment (CWE-708) vulnerability in Canonical Juju. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12815
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations on resource access, which structurally prevents assignment of ownership outside the intended control sphere.
Provides the mechanism to associate and manage security attributes such as ownership, directly stopping incorrect owner assignment.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Defining, enforcing and reviewing access permissions and entitlements directly addresses correct ownership assignment for resources.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access-control policy can mandate correct ownership assignment, but does not prescribe how ownership is technically enforced.
Identity-management processes define who may own resources, yet do not guarantee correct assignment at creation time.
Access-rights provisioning includes ownership assignment; fixing CWE-708 directly supports this control's intent.
Role definitions can require ownership accountability, but the control itself does not address technical assignment errors.
Privileged-access rules often include ownership checks, yet the control focuses on elevated rights rather than ownership correctness.
Information-access-restriction mechanisms rely on correct ownership; eliminating incorrect ownership strengthens this control.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
RHEL 7 (1 rule)
- V-204392 The Red Hat Enterprise Linux operating system must be configured so that the file permissions, ownership, and group membership of system files and commands match the vendor values. prevents CWE-708