Cross-application secret access via predictable identifiers
Published Mar 18, 2026 · Updated Mar 18, 2026
Authorization bypass in Canonical Juju 3.0.0 through 3.6.18 allows remote authenticated users to access another application's secrets. Juju provides no API for a grantee to verify a granted secret's owner, while time, process, machine and counter data make sibling XIDs predictable. Exploitation requires attacker control of one of two applications related to the same provider, enabling secret disclosure or access to resources held by the other application.
Summary
What happened
Authorization bypass in Canonical Juju 3.0.0 through 3.6.18 allows remote authenticated users to access another application's secrets. Juju provides no API for a grantee to verify a granted secret's owner, while time, process, machine and counter data make sibling XIDs predictable. Exploitation requires attacker control of one of two applications related to the same provider, enabling secret disclosure or access to resources held by the other application.
The record
- CVE
- CVE-2026-32694
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- Canonical
- Product
- Juju
- Classifications
- CWE-343, CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0 <3.6.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Canonical confused-deputy IDOR proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo