How severe is GHSA-j6f6-jp3p-53mw?

GHSA-j6f6-jp3p-53mw has a CVSS score of 4.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-j6f6-jp3p-53mw?

GHSA-j6f6-jp3p-53mw affects the following packages: github.com/juju/juju (Go). Ecosystems affected: Go.

How do I fix GHSA-j6f6-jp3p-53mw?

Update github.com/juju/juju to 0.0.0-20250623030540-c91a1f404695 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j6f6-jp3p-53mw is resolved across your whole dependency graph.

How do I detect GHSA-j6f6-jp3p-53mw in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/juju/juju. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-j6f6-jp3p-53mw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-j6f6-jp3p-53mw?

O3 pinpoints whether GHSA-j6f6-jp3p-53mw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-j6f6-jp3p-53mw actively exploited in the wild?

No public exploit code has been indexed for GHSA-j6f6-jp3p-53mw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-j6f6-jp3p-53mw?

GHSA-j6f6-jp3p-53mw is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j6f6-jp3p-53mw published, and has it been updated?

GHSA-j6f6-jp3p-53mw was published on April 3, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-j6f6-jp3p-53mw

MEDIUM

GHSA-j6f6-jp3p-53mw is a medium-severity (CVSS 4.9) CWE-863 vulnerability in github.com/juju/juju. O3 Security confirms whether GHSA-j6f6-jp3p-53mw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Juju: Read All Controller Logs From Compromised Workload

Also known asCVE-2025-68152GO-2026-5451

Published

Apr 3, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/juju/juju

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 is where the authorizer is defined for the endpoint.
here is where the authorizer is checked.
here 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/juju/juju`	all versions	0.0.0-20250623030540-c91a1f404695

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/juju/juju. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/juju/juju to 0.0.0-20250623030540-c91a1f404695 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j6f6-jp3p-53mw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j6f6-jp3p-53mw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j6f6-jp3p-53mw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ###

O3 Security · Impact-Aware SCA

Is GHSA-j6f6-jp3p-53mw in your dependencies?

O3 detects GHSA-j6f6-jp3p-53mw across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works