# CVE-2025-68153: Juju: Resource poisoning

> Authenticated users can modify application resources across the entire controller due to missing authorization checks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 3 Apr 2026
- **Updated:** 4 Apr 2026
- **Also known as:** GHSA-245v-p8fj-vwm2, GO-2026-4924

## What is CVE-2025-68153?

CVE-2025-68153 is a high-severity missing authorization vulnerability in juju, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Juju is an open source application orchestration engine that enables any application operation on any infrastructure at any scale through special operators called ‘charms’. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, any authenticated user, machine or controller under a Juju controller can modify the resources of an application within the entire controller. This issue has been patched in versions 2.9.56 and 3.6.19.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-68153?

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-20260120044552-26ff93c903d5 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20260120044552-26ff93c903d5 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20260120044552-26ff93c903d5 |

Products: Canonical Juju.

## How do I fix CVE-2025-68153?

Upgrade github.com/juju/juju to 0.0.0-20260120044552-26ff93c903d5 or later.

## Is CVE-2025-68153 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68153 exists.

## Other vulnerabilities in 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-2026-5412](https://insights.sbomify.com/CVE-2026-5412/): Juju CloudSpec API could leak senstive information (critical 9.9)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68153 and fix it if it is affected.

What it is: CVE-2025-68153 is a high-severity missing authorization vulnerability in juju, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68153 exists.

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

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-2025-68153/ (Markdown: https://insights.sbomify.com/CVE-2025-68153/index.md)
```

## Sources

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

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