Quick answers
- Is CVE-2026-93336 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93336 being exploited in the wild.
- How severe is CVE-2026-93336?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Canonical Juju 4.0 through 4.0.15.
- Is there a fix for CVE-2026-93336?
- Yes: fixed in 4.0.16 and later. Until then: Restrict controller access to trusted principals only, and avoid storing sensitive credentials such as container-registry secrets in charm resources until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93336 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-93336?
- Check whether you run Canonical Juju at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.0.16 and later
Restrict controller access to trusted principals only, and avoid storing sensitive credentials such as container-registry secrets in charm resources until upgrading.
Technical details
The GET /model/:modeluuid/units/:unit/resources/:resource endpoint was registered with a TODOAuthorizer and dropped authorization context tags during a 4.0 rewrite, allowing unauthenticated resource access. Any controller-authenticated principal—including a user with only login permission or a unit agent from another application—can bypass the check and stream arbitrary charm resources. The fix restricts the route to unit and application agents, requiring the authenticated tag to match the requested unit.
Affected products
- Canonical Juju 4.0 through 4.0.15
Timeline
- 2026-10-22: disclosed
- 2026-10-07: patched