CVE-2026-93336

waiting for further signalsZero needs more public information before it can validate it.

GHSA-43hf-rrv4-hhf5 ↗EUVD-2026-108266 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Canonical Juju >= 4.0, < 4.0.16
fixed in 4.0.16
ETK-2026-2488Zero's internal tracking ID, independent of the CVE number., permanent identifier
40msince last run
1h 07mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h57m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Canonical Juju 4.0 through 4.0.15 does not properly enforce authorization on unit resource downloads. A principal authenticated to the controller may access charm resources outside its intended scope, potentially exposing registry credentials. Exploitation requires controller authentication, including credentials for a unit agent or a login-only user.

mitigation

Upgrade juju to 4.0.16 or later.

fixed in 4.0.16

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 07m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 17:32Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-22 17:32Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 17:32Z

this entry in the feed

GET /api/v1/feed/CVE-2026-93336

{
  "etk_id": "ETK-2026-2488",
  "cve_id": "CVE-2026-93336",
  "display_id": "CVE-2026-93336",
  "ghsa_id": "GHSA-43hf-rrv4-hhf5",
  "euvd_id": "EUVD-2026-108266",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization for Juju unit resource downloads",
  "summary": "Canonical Juju 4.0 through 4.0.15 does not properly enforce authorization on unit resource downloads. A principal authenticated to the controller may access charm resources outside its intended scope, potentially exposing registry credentials. Exploitation requires controller authentication, including credentials for a unit agent or a login-only user.",
  "mitigation": "Upgrade juju to 4.0.16 or later.",
  "vendor": "Canonical",
  "product": "Juju",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0, < 4.0.16"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.0.16"
      ],
      "package_name": "juju",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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/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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 66.67849698333333,
  "t0_at": "2026-10-22T17:32:13.820000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T17:32:13.820000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T17:32:13.820000+00:00",
      "url": "https://github.com/advisories/GHSA-43hf-rrv4-hhf5"
    }
  }
}

published 2026-10-22 19:22Z
last change 2026-10-22 20:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.