# Juju vulnerable to sensitive log retrieval via authenticated endpoint without authorization in github.com/juju/juju

Advisory record · `GHSA-r64v-82fh-xc63`

- **Identifiers:** `GHSA-r64v-82fh-xc63` · `CVE-2025-53512` · `GO-2025-3806`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-285](https://cwe.mitre.org/data/definitions/285.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 28 Jul 2025
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Jul 2025, 19:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/juju/juju` (Go): affected `<0.0.0-20250619024904-402ff008dcc2`; fixed in `0.0.0-20250619024904-402ff008dcc2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Juju (github.com/juju/juju) versions before 0.0.0-20250619024904-402ff008dcc2 are affected. An authenticated user can retrieve sensitive log data through an endpoint that does not enforce authorization checks. The source gives few details beyond this. Upgrade to 0.0.0-20250619024904-402ff008dcc2 or later.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (canonical)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0038, the 32nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 28 Jul 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-r64v-82fh-xc63](https://github.com/advisories/GHSA-r64v-82fh-xc63)
- [OSV: GHSA-r64v-82fh-xc63](https://osv.dev/vulnerability/GHSA-r64v-82fh-xc63)
- <https://github.com/juju/juju/security/advisories/GHSA-r64v-82fh-xc63>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-53512>
- <https://github.com/juju/juju/commit/402ff008dcc2cb57f4441968628637efb5c2a662>
- <https://github.com/juju/juju/commit/c91a1f4046956874ba77c8b398aecee3d61a2dc3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r64v-82fh-xc63>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r64v-82fh-xc63/>. Everything for agents: <https://agentprime.io/llms.txt>.
