CVE-2025-68152: Juju Read All Controller Logs From Vulnerability

MODERATE
Advisory Identifier: GHSA-j6f6-jp3p-53mw
Share
CVSS 4.9
CWE-863
Published
Advisory Summary

CVE-2025-68152 is a MODERATE (CVSS 4.9) read all controller logs from vulnerability (CWE-863: Incorrect Authorization) affecting Juju libraries in the Go ecosystem. The issue involves read all controller logs from compromised workload. Remediation is available by upgrading affected packages to version 0.0.0-20250623030540-c91a1f404695.

CVE-2025-68152 at a Glance

CVE Identifier CVE-2025-68152
GHSA Identifier GHSA-j6f6-jp3p-53mw
Severity MODERATE
CVSS v3.1 Base Score 4.9
CWE Classification CWE-863: Incorrect Authorization
Affected Product Juju
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-68152

To remediate this vulnerability, upgrade all affected Juju dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/juju/juju fixed: 0.0.0-20250623030540-c91a1f404695 
Upgrade github.com/juju/juju to 0.0.0-20250623030540-c91a1f404695
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/juju/juju

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-68152, inspect your project dependencies for Juju:

inspect dependencies for github.com/juju/juju

Analyze the terminal output to locate any version of Juju in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20250623030540-c91a1f404695), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Juju, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary It is possible that a compromised workload machine under a Juju controller can read any log file for any entity in any model at any level. There is a debug log endpoint in the API server that allows streaming of logs off of the controller. To access this endpoint you must be authentication and either be a machine agent, controller agent, controller admin or have model read permission. The problematic is the machine agent story. The rest of the other checks have a high enough degree of safety that an attacker can not move side ways in the controller when obtaining log files. ### Details A compromised workload machine is capable of obtaining logs for both the controller and any model under the controller at any log level they wish. A bad actor can use this information as signal for further attacks or possible gain secret information leaked out in debug and trace logs. On top of this they would also be able to receive the logs from the charm itself for which we have no control over. - [here](https://github.com/juju/juju/blob/1a8d84ec114c2e4f9921e30081e5a5549f7cbfc4/apiserver/apiserver.go#L767) is where the authorizer is defined for the endpoint. - [here](https://github.com/juju/juju/blob/1a8d84ec114c2e4f9921e30081e5a5549f7cbfc4/apiserver/debuglog.go#L110) is where the authorizer is checked. - [here](https://github.com/juju/juju/blob/1a8d84ec114c2e4f9921e30081e5a5549f7cbfc4/apiserver/debuglog.go#L115) and onwards is the amount of information the attacker can gain access to. ### PoC If an attacker compromises a workload machine, they will have access to the agent.conf file containing the credentials. This can then be used to obtain debug logs for any part of the controller.

CVE-2025-68152 Affected Juju Versions

1 component(s)
Fixed Versions:
0.0.0-20250623030540-c91a1f404695
Product / Package Ecosystem Affected Versions Fixed Version
github.com/juju/juju
golang/github.com/juju/juju
Go
< 0.0.0-20250623030540-c91a1f404695
0.0.0-20250623030540-c91a1f404695

References

GitHub Advisory / Wiki ADVISORY
https://github.com/juju/juju/security/advisories/GHSA-j6f6-jp3p-53mw
NVD — CVE-2025-68152 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-68152
Security Fix Commit FIX COMMIT
https://github.com/juju/juju/commit/22cdcf6b54c2f371822e1c203d4f341be6c9589e
Security Fix Commit FIX COMMIT
https://github.com/juju/juju/commit/c91a1f4046956874ba77c8b398aecee3d61a2dc3
Juju Source Repository REPOSITORY
https://github.com/juju/juju

Frequently Asked Questions

What is CVE-2025-68152?
CVE-2025-68152 is a security vulnerability in Juju involving Read All Controller Logs From Compromised Workload under CWE-863: Incorrect Authorization.
Which Juju versions are affected?
Affected versions include releases prior to 0.0.0-20250623030540-c91a1f404695 across affected packages: github.com/juju/juju.
What version fixes CVE-2025-68152?
Upgrading to 0.0.0-20250623030540-c91a1f404695 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/juju/juju affected?
Yes, github.com/juju/juju is affected in releases prior to 0.0.0-20250623030540-c91a1f404695. Upgrade your dependency to 0.0.0-20250623030540-c91a1f404695 or later.
What is the CVSS score of CVE-2025-68152?
CVE-2025-68152 has a CVSS v3.1 base score of 4.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2025-68152?
CVE-2025-68152 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2025-68152?
Run the dependency tree command: 'inspect dependencies for github.com/juju/juju'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j6f6-jp3p-53mw",
  "modified" : "2026-04-27T16:43:44Z",
  "published" : "2026-04-03T18:18:38Z",
  "aliases" : [ "CVE-2025-68152" ],
  "summary" : "Juju: Read All Controller Logs From Compromised Workload",
  "details" : "### Summary\nIt is possible that a compromised workload machine under a Juju controller can read any log file for any entity in any model at any level.\n\nThere is a debug log endpoint in the API server that allows streaming of logs off of the controller. To access this endpoint you must be authentication and either be a machine agent, controller agent, controller admin or have model read permission.\n\nThe problematic is the machine agent story. The rest of the other checks have a high enough degree of safety that an attacker can not move side ways in the controller when obtaining log files.\n\n### Details\nA compromised workload machine is capable of obtaining logs for both the controller and any model under the controller at any log level they wish. A bad actor can use this information as signal for further attacks or possible gain secret information leaked out in debug and trace logs. On top of this they would also be able to receive the logs from the charm itself for which we have no control over.\n\n- [here](https://github.com/juju/juju/blob/1a8d84ec114c2e4f9921e30081e5a5549f7cbfc4/apiserver/apiserver.go#L767) is where the authorizer is defined for the endpoint.\n- [here](https://github.com/juju/juju/blob/1a8d84ec114c2e4f9921e30081e5a5549f7cbfc4/apiserver/debuglog.go#L110) is where the authorizer is checked.\n- [here](https://github.com/juju/juju/blob/1a8d84ec114c2e4f9921e30081e5a5549f7cbfc4/apiserver/debuglog.go#L115) and onwards is the amount of information the attacker can gain access to.\n\n### PoC\n\nIf an attacker compromises a workload machine, they will have access to the agent.conf file containing the credentials. This can then be used to obtain debug logs for any part of the controller.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/juju/juju"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20250623030540-c91a1f404695"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/juju/juju/security/advisories/GHSA-j6f6-jp3p-53mw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-68152"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/juju/juju/commit/22cdcf6b54c2f371822e1c203d4f341be6c9589e"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/juju/juju/commit/c91a1f4046956874ba77c8b398aecee3d61a2dc3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/juju/juju"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-03T18:18:38Z",
    "nvd_published_at" : "2026-04-03T16:16:23Z"
  }
}