Canonical Juju up to 3.6.18 incorrect ownership assignment
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Canonical Juju up to 3.6.18 and classified as problematic. This vulnerability affects unknown code. Such manipulation leads to incorrect ownership assignment. This vulnerability is referenced as CVE-2026-32691. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Canonical Juju up to 3.6.18. It has been rated as problematic. Affected by this issue is an unknown code. The manipulation with an unknown input leads to a incorrect ownership assignment vulnerability. Using CWE to declare the problem leads to CWE-708. The product assigns an owner to a resource, but the owner is outside of the intended control sphere. Impacted is confidentiality. CVE summarizes:
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.
The weakness was published by Harry Pidcock as GHSA-gfgr-6hrj-85ww. The advisory is available at github.com. This vulnerability is handled as CVE-2026-32691 since 03/13/2026. The exploitation is known to be difficult. The attack may be launched remotely. The technical details are unknown and an exploit is not available.
Upgrading to version 3.6.19 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 3.6.0
- 3.6.1
- 3.6.2
- 3.6.3
- 3.6.4
- 3.6.5
- 3.6.6
- 3.6.7
- 3.6.8
- 3.6.9
- 3.6.10
- 3.6.11
- 3.6.12
- 3.6.13
- 3.6.14
- 3.6.15
- 3.6.16
- 3.6.17
- 3.6.18
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (canonical): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrect ownership assignmentCWE: CWE-708 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Juju 3.6.19
Timeline
03/13/2026 CVE reserved03/18/2026 Advisory disclosed
03/18/2026 VulDB entry created
03/24/2026 VulDB entry last update
Sources
Advisory: GHSA-gfgr-6hrj-85wwResearcher: Harry Pidcock
Status: Confirmed
CVE: CVE-2026-32691 (🔒)
GCVE (CVE): GCVE-0-2026-32691
GCVE (VulDB): GCVE-100-351530
Entry
Created: 03/18/2026 15:21Updated: 03/24/2026 16:47
Changes: 03/18/2026 15:21 (64), 03/24/2026 16:47 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.