Cyber Resilience

CVE-2025-68153

Access Control in Canonical Juju 2.9 – 2.9.55

Published
03 April 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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.0023 14th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2025-68153 is a high-severity Incorrect Authorization (CWE-863) vulnerability in Canonical Juju. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 14th 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 AC-6 (Least Privilege) — 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, any authenticated user, machine or…

more

controller under a Juju controller can modify the resources of an application within the entire controller. This issue has been patched in versions 2.9.56 and 3.6.19.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1578.005 Modify Cloud Compute Configurations Defense Impairment
Adversaries may modify settings that directly affect the size, locations, and resources available to cloud compute infrastructure in order to evade defenses.
Why these techniques?

CWE-863 authz flaw allows any authenticated entity to modify app resources controller-wide, directly enabling privilege escalation and unauthorized config changes in the orchestration system.

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

CVEs Like This One

CVE-2025-68152Same product: Canonical Juju
CVE-2026-32693Same product: Canonical Juju
CVE-2026-32692Same product: Canonical Juju
CVE-2025-0928Same product: Canonical Juju
CVE-2026-32691Same 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
  • AC-6 Least Privilege
  • CM-5 Access Restrictions for Change
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 to block authenticated principals from modifying application resources outside their permitted scope.

prevent

Requires assignment of only the minimum privileges needed, preventing the broad cross-application modification rights exposed by the flaw.

prevent

Restricts the ability to perform configuration or resource changes to authorized entities only, directly limiting the unauthorized modification vector.

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