immich before 3.0.3 contains a broken access control vulnerability in the PUT /albums/:id/user/:userId endpoint that allows shared album editors to modify member roles without owner-only restrictions. Attackers with editor access can demote the album owner to editor and promote themselves to owner in sequential requests, gaining full control including deletion and eviction capabilities.
CVE-2026-59258
This high-severity CVE scores 8.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- EG Score
- 8.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (5)
Auto-updated Jul 15, 2026immich < 3.0.3 Shared Album Editor Ownership Takeover via updateUser | Advisories | VulnCheck
https://www.vulncheck.com/advisories/immich-shared-album-editor-ownership-takeover-via-updateuserv3.0.3
Patch available: immich-app/immich v3.0.3
https://github.com/immich-app/immich/releases/tag/v3.0.3fix: unauthorized album owner update
Fix merged in immich-app/immich PR #29883 on 2026-07-13 — awaiting tagged release
https://github.com/immich-app/immich/pull/29883Album takeover / role-management privilege escalation by a shared Editor (broken access control in `updateUser`) · Issue #29857 · immich-app/immich · GitHub
https://github.com/immich-app/immich/issues/29857commit 84dff19ca9a4 (immich-app/immich)
Fix landed in immich-app/immich commit 84dff19ca9a4 — awaiting tagged release
https://github.com/immich-app/immich/commit/84dff19ca9a467752d848ff54763d62c04ebf960Vendor Advisories for CVE-2026-59258(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 17:29 UTCEG score recompute
- 2026-07-15 17:28 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-59258?
When was CVE-2026-59258 disclosed?
What is the CVSS score of CVE-2026-59258?
How do I remediate CVE-2026-59258?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59258
Is Your Infrastructure Affected by CVE-2026-59258?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.