# CVE-2026-93336: Missing authorization in the unit resources download route in Juju controllers


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-43hf-rrv4-hhf5, GHSA-fp7x-6hq5-3c3w

## What is CVE-2026-93336?

CVE-2026-93336 is a high-severity vulnerability in Canonical Juju, published on 22 Oct 2026. 

### Official description

Missing authorization in the unit resources download route in Canonical Juju 4.0 through 4.0.15 allows a controller-authenticated principal (a unit agent, or a user with only login permission) to read any application's charm resource in any model,  including container-registry credentials, via a crafted request naming an arbitrary unit.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-93336?


## How do I fix CVE-2026-93336?

No fix has been published for CVE-2026-93336 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93336 being exploited?

There is no known exploitation of CVE-2026-93336 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93336 and fix it if it is affected.

What it is: CVE-2026-93336 is a high-severity vulnerability in Canonical Juju, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93336 in the wild and no public exploit code.

Affected product: Canonical Juju. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93336/ (Markdown: https://insights.sbomify.com/CVE-2026-93336/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93336
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93336
- OSV: https://osv.dev/vulnerability/CVE-2026-93336

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93336/
Summaries are generated and may contain mistakes; the official description above is the record.