Is CVE-2025-68152 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-68152 being exploited in the wild.

How severe is CVE-2025-68152?

Medium severity, with a CVSS score of 4.9, published 3 April 2026.

Which products and versions are affected?

Canonical Juju 2.9 to 2.9.55, 3.6 to 3.6.18; github.com/juju/juju (Go) < 0.0.0-20250623030540-c91a1f404695, SEMVER:introduced=0,fixed=0.0.0-20250623030540-c91a1f404695.

Is there a fix for CVE-2025-68152?

Yes. github.com/juju/juju (Go): upgrade to 0.0.0-20250623030540-c91a1f404695 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-68152 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2025-68152?

Check whether you run Canonical Juju or github.com/juju/juju (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-68152: Canonical Juju Incorrect Authorization in Debug Log Endpoint

Q: Is there a fix for CVE-2025-68152?

Yes. github.com/juju/juju (Go): upgrade to 0.0.0-20250623030540-c91a1f404695 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2025-68152 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2025-68152?

Check whether you run Canonical Juju or github.com/juju/juju (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-68152 · Severity: medium · CVSS 4.9 · Published 2026-04-03

Juju is an application orchestration engine used to deploy and manage software across various cloud infrastructures. A security flaw allows a compromised machine within the environment to access sensitive log files from across the entire management system. This could lead to the exposure of administrative secrets or operational data, potentially facilitating further attacks on the infrastructure.

Technologies: Canonical Juju, github.com/juju/juju (Go). Vendors: Canonical, Go.

Quick answers

Is CVE-2025-68152 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-68152 being exploited in the wild.
How severe is CVE-2025-68152?: Medium severity, with a CVSS score of 4.9, published 3 April 2026.
Which products and versions are affected?: Canonical Juju 2.9 to 2.9.55, 3.6 to 3.6.18; github.com/juju/juju (Go) < 0.0.0-20250623030540-c91a1f404695, SEMVER:introduced=0,fixed=0.0.0-20250623030540-c91a1f404695.
Is there a fix for CVE-2025-68152?: Yes. github.com/juju/juju (Go): upgrade to 0.0.0-20250623030540-c91a1f404695 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-68152 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2025-68152?: Check whether you run Canonical Juju or github.com/juju/juju (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/juju/juju (Go): upgrade to 0.0.0-20250623030540-c91a1f404695 or later
```
go get github.com/juju/juju@v0.0.0-20250623030540-c91a1f404695
```

Technical details

An incorrect authorization vulnerability (CWE-863) exists in the Juju API server's debug log endpoint. While the endpoint requires authentication, it fails to properly restrict machine agents to their own logs, allowing a compromised workload machine to use its credentials to stream logs for any entity, model, or the controller itself at any log level. This can result in the exposure of sensitive information leaked in debug or trace logs. The issue is fixed in Juju versions 2.9.56 and 3.6.19 by ensuring the authorizer correctly validates model-level permissions.

Affected products

Canonical Juju 2.9 to 2.9.55, 3.6 to 3.6.18

Identifiers

CVE-2025-68152
GHSA-j6f6-jp3p-53mw
GO-2026-5451

Timeline

2026-04-01: advisory: Vendor advisory published on GitHub
2026-04-03: disclosed: CVE published to NVD
2026-04-03: patched: Patches released in versions 2.9.56 and 3.6.19

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.