dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-59258

HIGH · 8.3 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

immich before 3.0.3 has a broken access control vulnerability in the PUT /albums/:id/user/:userId endpoint where shared album editors can modify member roles without owner-only restrictions. Attackers with editor access can sequentially demote the album owner to editor and promote themselves to owner, gaining full control including deletion and eviction capabilities.

MitigationUpdate immich to version 3.0.3 or later, which should contain proper authorization checks enforcing that only album owners can modify member roles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify immich installation version
    Query the immich API server-info endpoint (e.g., GET /api/server-info) or check the docker container labels/environment variables for the IMICH_VERSION variable. If using the web UI, navigate to Administration > Settings > General to view the server version.
    Affected if The installed version is before 3.0.3 (e.g., 3.0.2, 3.0.1, 3.0.0, or any 2.x.x release)
  2. Verify shared album functionality is in use
    Check if any user accounts in immich have access to shared albums. Use the API endpoint GET /api/albums and filter for albums where shared=true or check the sharedWith array. Alternatively, query the database (albums table) for entries where the sharedUsers column is not null or empty.
    Affected if Shared albums exist and non-owner users (editors) have access to them, making the vulnerable endpoint reachable
  3. Confirm user role assignment in shared albums
    As a user with editor privileges on a shared album, inspect your access by calling GET /api/albums/:id to view the assets/sharedUsers structure. Verify that your user account appears in the sharedUsers array with role=editor. This confirms you have the elevated access level needed to exploit the flaw.
    Affected if You hold editor role on any shared album and can view your role via the API or UI
  4. Test role modification endpoint authorization
    As a non-owner (editor) user on a shared album, attempt to call PUT /api/albums/:id/user/:userId with a payload containing a different role (e.g., {"role": "owner"}). Use a tool like curl or Postman with an authenticated session token. Check if the request succeeds and returns 200 OK instead of being rejected with 403 Forbidden.
    Affected if The PUT request succeeds and allows an editor to modify their own or another user's role without owner authentication, confirming the broken access control exists

You are affected if immich version is below 3.0.3 AND you have editor-level access to any shared album, as the broken access control in the role modification endpoint allows unauthorized role escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update immich to version 3.0.3 or later, which should contain proper authorization checks enforcing that only album owners can modify member roles.

Recommended fix High confidence

immich version 3.0.3 or later

  1. Back up your immich database and data directory before upgrading
  2. Stop the immich server and related services
  3. Update immich to version 3.0.3 or later using your deployment method (Docker, Kubernetes, or package manager)
  4. Restart the immich services
  5. Verify the application starts successfully and check the version number
  6. Test that the album user role modification endpoint now properly enforces owner-only restrictions
Caveat Review immich release notes for 3.0.3; minor version upgrades typically have minimal breaking changes but verify any migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59258 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59258 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data