Secret poisoning via overbroad Vault token policy
Published Mar 18, 2026 · Updated Mar 18, 2026
Improper authorization in Canonical Juju 3.1.6 through 3.6.18 allows remote authenticated users to overwrite Vault secret revisions. The Vault RestrictedConfig path grants agent tokens create access across the model mount instead of limiting writes to secret identifiers owned by that agent. Exploitation requires an authenticated unit agent and sufficient revision information; successful writes poison existing revisions in the model's Vault back end.
Summary
What happened
Improper authorization in Canonical Juju 3.1.6 through 3.6.18 allows remote authenticated users to overwrite Vault secret revisions. The Vault RestrictedConfig path grants agent tokens create access across the model mount instead of limiting writes to secret identifiers owned by that agent. Exploitation requires an authenticated unit agent and sufficient revision information; successful writes poison existing revisions in the model's Vault back end.
The record
- CVE
- CVE-2026-32692
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- Canonical
- Product
- Juju
- Classifications
- CWE-285, T1565.001
- 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.1.6 <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.
Public exploit references
No public exploit references are available in this record.
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