CVE-2026-93336 Canonical CVE debrief

Who should care

Defenders responsible for Canonical Juju deployments, especially those using versions 4.0 through 4.0.15, should assess their exposure and prioritize remediation. This vulnerability could impact environments where unauthorized access to charm resources could compromise security.

Why it matters

CVE-2026-93336 is a high-severity vulnerability in Canonical Juju that allows controller-authenticated principals to read any application's charm resource. Defenders should prioritize verifying and remediating this issue, especially in environments using affected versions, as it could lead to unauthorized access to sensitive resources.

• Potential unauthorized access to sensitive charm resources
• Possible exposure of container-registry credentials
• Need for verification of Canonical Juju versions in use
• Prioritization of patching or updating vulnerable deployments

Technical summary

The vulnerability exists in the unit resources download route in Canonical Juju 4.0 through 4.0.15. A controller-authenticated principal, such as a unit agent or a user with only login permission, can read any application's charm resource in any model by crafting a request naming an arbitrary unit. This could lead to unauthorized access to sensitive information, including container-registry credentials.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability, especially in environments using Canonical Juju 4.0 through 4.0.15, as it could allow unauthorized access to sensitive resources.

Recommended defensive actions

• Verify the version of Canonical Juju in use and assess exposure
• Restrict access to sensitive resources and ensure proper authorization
• Monitor for suspicious activity related to charm resource access
• Apply patches or updates provided by the vendor once available
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, including its description, CVSS score, and references to source-specific information. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.