CVE-2026-77439

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

GHSA-c9mf-h82r-8p4j ↗EUVD-2026-117614 ↗

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.
immich-app immich <= 3.0.0
fixed in v3.0.3
CWE-269 Improper Privilege Management
ETK-2026-3655Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/immich
4h 46msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Immich releases before 3.0.3 are affected by an authorization flaw in shared-album role management. An authenticated user with editor access to a shared album can obtain owner-level control, potentially removing the original owner or deleting the album.

mitigation

Upgrade Immich to version 3.0.3 or later. Until the upgrade is complete, limit editor access to shared albums to trusted users.

fixed in v3.0.3

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
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 17:25Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-05 17:25Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3655",
  "cve_id": "CVE-2026-77439",
  "display_id": "CVE-2026-77439",
  "ghsa_id": "GHSA-c9mf-h82r-8p4j",
  "euvd_id": "EUVD-2026-117614",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper album ownership authorization in Immich",
  "summary": "Immich releases before 3.0.3 are affected by an authorization flaw in shared-album role management. An authenticated user with editor access to a shared album can obtain owner-level control, potentially removing the original owner or deleting the album.",
  "mitigation": "Upgrade Immich to version 3.0.3 or later. Until the upgrade is complete, limit editor access to shared albums to trusted users.",
  "vendor": "immich-app",
  "product": "immich",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.0.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "v3.0.3"
      ],
      "package_name": "immich",
      "purl": "pkg:npm/immich"
    }
  ],
  "cwes": [
    269
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.208022416666665,
  "t0_at": "2026-11-05T17:25:59.809000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T17:25:59.809000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T17:25:59.809000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-77439"
    }
  }
}

published 2026-11-05 17:46Z
last change 2026-11-05 20:10Z

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.