Cyber Resilience

CVE-2025-68152

Access Control in Canonical Juju 2.9 – 2.9.55

Published
03 April 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0036 29th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-68152 is a medium-severity Incorrect Authorization (CWE-863) vulnerability in Canonical Juju. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AU-9 (Protection of Audit Information) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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, it is possible that a…

more

compromised workload machine under a Juju controller can read any log file for any entity in any model at any level. This issue has been patched in versions 2.9.56 and 3.6.19.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Why these techniques?

Vulnerability enables unauthorized file reads of logs on controller from compromised workload, directly facilitating data collection from local system storage.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-68153Same product: Canonical Juju
CVE-2026-32693Same product: Canonical Juju
CVE-2025-0928Same product: Canonical Juju
CVE-2026-32691Same product: Canonical Juju
CVE-2026-32692Same product: Canonical Juju
CVE-2026-32694Same product: Canonical Juju
CVE-2025-53513Same product: Canonical Juju
CVE-2023-0092Same product: Canonical Juju
CVE-2024-8037Same product: Canonical Juju
CVE-2026-5774Same product: Canonical Juju

Affected Assets

canonical
juju
2.9 — 2.9.55 · 3.6 — 3.6.18

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AU-9 Protection of Audit Information
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authorization checks on log file access so a compromised workload cannot read logs belonging to other entities or models.

prevent

Requires cryptographic or access-control protection of audit/log information, directly blocking the unauthorized cross-entity log reads described in the CVE.

prevent

Limits privileges granted to workload machines so they receive only the minimum rights needed, reducing the impact of a compromise on other models' logs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Defining, enforcing, and reviewing access authorizations and least privilege directly prevents incorrect authorization checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

prevents

Enforcing policy-driven approval and role-change reviews stops incorrect or stale authorization decisions from remaining in effect after job changes or terminations.

prevents

By tying access rights to identity, device, location and classification, the control reduces the likelihood that an authorization decision will be based on an incorrect or bypassed policy.

References