# CVE-2026-5412: Juju CloudSpec API could leak senstive information

> An authenticated low-privileged user can access sensitive cloud credentials via the CloudSpec API due to missing authorization checks.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-w5fq-8965-c969, GO-2026-5692

## What is CVE-2026-5412?

CVE-2026-5412 is a critical missing authorization vulnerability in Canonical Juju, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Juju versions prior to 2.9.57 and 3.6.21, an authorization issue exists in the Controller facade. An authenticated user can call the CloudSpec API method to extract the cloud credentials used to bootstrap the controller. This allows a low-privileged user to access sensitive credentials. This issue is resolved in Juju versions 2.9.57 and 3.6.21.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-5412?

3 open source packages ship an affected version, including github.com/juju/juju. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20260408003526-d395054dc2c3 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20260408003526-d395054dc2c3 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20260408003526-d395054dc2c3 |

Products: Canonical Juju.

## How do I fix CVE-2026-5412?

Upgrade github.com/juju/juju to 0.0.0-20260408003526-d395054dc2c3 or later.

## Is CVE-2026-5412 being exploited?

There is no known exploitation of CVE-2026-5412 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Juju

- [CVE-2026-4370](https://insights.sbomify.com/CVE-2026-4370/): Improper TLS Client/Server authentication and certificate verification on Database Cluster (critical 10.0)
- [CVE-2017-9232](https://insights.sbomify.com/CVE-2017-9232/): Juju uses a UNIX domain socket without setting appropriate permissions (critical 9.8)
- [CVE-2026-32693](https://insights.sbomify.com/CVE-2026-32693/): Unauthorized access to Kubernetes secrets in Juju (high 8.8)
- [CVE-2025-0928](https://insights.sbomify.com/CVE-2025-0928/): Arbitrary executable upload via authenticated endpoint (high 8.8)
- [CVE-2025-53513](https://insights.sbomify.com/CVE-2025-53513/): Zip slip vulnerability in Juju (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5412 and fix it if it is affected.

What it is: CVE-2026-5412 is a critical missing authorization vulnerability in Canonical Juju, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5412 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20260408003526-d395054dc2c3
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20260408003526-d395054dc2c3
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20260408003526-d395054dc2c3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5412/ (Markdown: https://insights.sbomify.com/CVE-2026-5412/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5412
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5412
- OSV: https://osv.dev/vulnerability/CVE-2026-5412

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5412/
Summaries are generated and may contain mistakes; the official description above is the record.