CVE-2026-32694
Predictable XID Allows Unauthorized Secret Access in Juju
Publication date: 2026-03-18
Last updated on: 2026-03-19
Assigner: Canonical Ltd.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| canonical | juju | From 3.0.0 (inc) to 3.6.19 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-343 | The product's random number generator produces a series of values which, when observed, can be used to infer a relatively small range of possibilities for the next value that could be generated. |
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-32694 is a vulnerability in Juju Secrets versions 3.0.0 through 3.6.18 where secret IDs are generated in a predictable, sequential manner (using XIDs). When a secret owner grants permissions to a grantee, the grantee relies solely on the secret ID to verify ownership without any additional verification of the secret's origin."}, {'type': 'paragraph', 'content': 'Because the secret IDs are predictable, a malicious grantee can guess secret IDs of past secrets granted by the same owner to other grantees. This allows the attacker to access and misuse secrets that were not intended for them.'}, {'type': 'paragraph', 'content': 'The attack requires a complex setup involving multiple applications, including one controlled by the attacker, and specific relation interfaces. The vulnerability is a form of Confused Deputy Insecure Direct Object Reference (IDOR), where the provider application unknowingly uses secret IDs on behalf of the attacker.'}] [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can lead to unauthorized access to secrets, allowing an attacker to exfiltrate or manipulate sensitive information and resources that were granted to other applications.
The impact affects confidentiality, integrity, and availability of the affected systems, potentially allowing attackers to misuse resources, disrupt operations, or compromise sensitive data.
Because the attack requires high privileges, network access, and a specific multi-application configuration, it is complex but can be difficult to detect after exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking for the use of predictable secret IDs and verifying secret ownership and grants within Juju workloads.
Suggested commands to assist in detection include:
- secret-ids --grants : Lists secret IDs along with their grant metadata, helping to identify if secret IDs are predictable or improperly shared.
- secret-info-get : Retrieves metadata about a secret, including owner, grant relation ID, and rotation policy, which can be used to verify secret provenance and detect unauthorized access.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Upgrade Juju to version 3.6.19 or later, where the vulnerability is patched.
- Use longer, cryptographically random secret IDs (e.g., adding a 128-bit nonce) to prevent guessing of secret IDs.
- Implement or enable a grantee secret API that verifies secret ownership and relation context before use, preventing unauthorized secret access.