VulnerabilityPublished 18 Mar 2026

CVE-2026-32691: Canonical Juju · Incorrect Ownership Assignment

Affects Canonical JujuSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.6.19 when convenient.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.6.19

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Juju and juju to 3.6.19.

Affected software

Product	Affected	Fixed in
CanonicalJuju	Affected >=3.0.0 <3.6.19	Fixed in 3.6.19
GitHubjuju/juju`pkg:github/juju/juju`Other threats	Affected =3.0.0	Fixed in–
GitHubjuju`pkg:github/juju`Other threats	Affected >=3.0.0 <3.6.19	Fixed in 3.6.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-32691, organizations should first apply any official patches or updates from Canonical once available. In the absence of patches, administrators should restrict and tightly control authentication and permissions for unit agents to minimize the number of entities capable of exploiting the race condition. Implementing strict access controls and monitoring for unusual unit agent behavior can help detect exploitation attempts. Additionally, consider reducing the lifetime or scope of secrets to limit exposure if compromised. Employing out-of-band verification or additional encryption layers for secrets may also reduce risk. Reviewing and hardening the Juju deployment configuration to minimize race condition windows, if possible, can be beneficial. Finally, maintain vigilant logging and auditing of secret creation and access events to identify potential exploitation.

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.

Impact

The primary impact of CVE-2026-32691 is the unauthorized disclosure of sensitive secrets managed by Juju, which can include credentials, API keys, or other confidential configuration data. This breach of confidentiality can lead to further compromise of cloud infrastructure, lateral movement within environments, and potential data exfiltration. Organizations relying on Juju for orchestration and secrets management may face increased risk of insider threats or compromised unit agents exploiting this vulnerability. Although the attack requires authenticated access as a unit agent, environments with multiple teams or automated agents increase the attack surface. The vulnerability does not affect integrity or availability directly but undermines trust in the secrets management process, potentially leading to broader security incidents. Given Juju's use in cloud and enterprise environments, the impact could be significant for organizations with complex deployments and sensitive workloads.

CWE-708Incorrect Ownership Assignment (opens in a new tab)
Base weakness
The product assigns an owner to a resource, but the owner is outside of the intended control sphere.
Policy
Periodically review the privileges and their owners.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/juju/juju/security/advisories/GHSA-gfgr-6hrj-85ww (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Mar 2026, 12:57 UTC

WeaknessesCWE-708

Technical details

References

Community reviews

Related threats