Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as accepted view-only partner
-
ExploitRequest /map/markers with withPartners=true and isArchived=true
-
ImpactEnumerate GPS coordinates and IDs of sharer's archived assets
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires an established view-only partner-sharing relationship: the attacker must be an authenticated low-privilege user whom the victim has accepted as a partner, and the victim must have archived assets carrying GPS metadata. The attacker then sets both withPartners=true and isArchived=true on GET /api/map/markers - the isArchived=true parameter is the specific trigger, as the contrast run (isArchived=false) correctly hides the assets. Limiting factors that reduce real-world risk: exploitation is confined to people the victim explicitly partnered with (not arbitrary remote attackers), no user interaction by the victim is needed, and the exposure is strictly location metadata and asset identifiers - image bytes remain protected by checkPartnerAccess. |
| Impact | This is a genuine but low-severity authorization/privacy flaw, not a high-urgency emergency. The vendor CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3 Medium) is internally consistent with the description: exploitation is over the network (AV:N), trivial (AC:L), requires an authenticated low-privilege actor (PR:L - specifically an accepted view-only partner), needs no user interaction (UI:N), and yields only limited confidentiality impact (C:L) with no integrity or availability loss. The SSVC-style 'this_month' decision label from vuln.today aligns with that: real but not act_now/emergency. A verified proof-of-concept is included in the advisory (poc.zip, reproduced 3/3 on v2.7.5), which raises practical exploitability, but this is still a bounded metadata-disclosure issue, not code execution or bulk data theft. No EPSS score was supplied and the CVE is NOT on the CISA KEV list, so there is no evidence of active exploitation - the signals point to a targeted privacy violation within an existing partner relationship rather than widespread opportunistic abuse. The main caveat: EPSS is missing from the input, so probabilistic exploitation likelihood cannot be cross-checked against the PoC availability. |
| Exploit ScenarioDerived | An Immich user shares their library view-only with a partner (e.g. a family member or ex-partner). That partner, authenticated to their own account, calls GET /api/map/markers?withPartners=true&isArchived=true and receives the GPS coordinates and asset IDs of the sharer's deliberately archived (hidden) photos and videos. A working PoC verifying this leak (returning lat/lon of an archived asset) is attached to the GHSA advisory and was reproduced on v2.7.5. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Immich before 3.0.0 leaks the GPS coordinates and asset identifiers of a sharer's archived photos and videos to view-only partner accounts through GET /api/map/markers. A partner who supplies both withPartners=true and isArchived=true causes the map repository to admit Archive-visibility rows for every selected owner, bypassing the non-archived-only boundary that the timeline endpoint and checkPartnerAccess both enforce. Impact is limited to location metadata and asset IDs (image bytes stay protected), and exploitation requires an already-accepted partner relationship; a proof-of-concept (poc.zip) accompanying the advisory was verified against v2.7.5, and the flaw is fixed in v3.0.0.
RemediationAI
Vendor-released patch: upgrade to Immich v3.0.0, which contains the fix from https://github.com/immich-app/immich/pull/29028 (commit b633cc4f046f198bc11648c486e1e6e3f19d26d5) and the release at https://github.com/immich-app/immich/releases/tag/v3.0.0; after upgrading, GET /api/map/markers?withPartners=true&isArchived=true no longer returns partner-owned archived assets, as covered by the new e2e assertions. The advisory does not document a supported workaround, so updating is the complete fix; if an upgrade must be staged, the exposure can be eliminated only by removing the attacker's partner access, since the caller controls both query parameters and the leaked records are the sharer's archived assets. Because the leaked data is limited to GPS coordinates and asset ids (image bytes remain gated by checkPartnerAccess), stripping location metadata from assets before archiving reduces what can be disclosed but does not close the authorization gap.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-639 (Authorization Bypass Through User-Controlled Key): the caller-controlled withPartners and isArchived query parameters steer which owner keys and which visibility classes the marker query honors. In server/src/services/map.service.ts the service starts with the caller's own user id and, when withPartners=true, appends the ids returned by getMyPartnerIds, so the repository receives a mixed set of owners. In server/src/repositories/map.repository.ts the isArchived=true branch then applies a where clause admitting either AssetVisibility.Timeline or AssetVisibility.Archive without constraining which owner each row belongs to, so archived assets of partner-owned ids are returned. The sibling code paths deliberately do not behave this way: timeline.service.ts throws when withPartners is combined with archived or trashed queries, and checkPartnerAccess in access.repository.ts only admits Timeline and Hidden visibility for partner assets, never Archive. The upstream fix (PR 29028) passes auth.user.id into getMapMarkers and changes the predicate to AND(asset.ownerId = authUserId, asset.visibility = Archive), keeping archived-asset visibility restricted to the caller's own library, and adds e2e tests asserting that the partner's archived asset id is absent while the caller's own archived asset id is present.
Know when Immich gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Network-reachable API, trivially triggered via a query parameter; PR:L because the attacker must be an authenticated accepted partner; only limited location-metadata disclosure, so C:L and I:N/A:N.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Immich is a high-performance self-hosted photo and video management solution. Prior to 3.0.0, GET /api/map/markers used server/src/services/map.service.ts to add partner owner identifiers when withPartners=true, while server/src/repositories/map.repository.ts applied Archive visibility to every selected owner when isArchived=true. A view-only partner could therefore enumerate the GPS coordinates and existence of a sharer's archived photos or videos even though the timeline and direct-access paths exclude archived partner assets. The exposure is limited to location metadata and asset identifiers because image bytes remain protected by checkPartnerAccess. This issue is fixed in version 3.0.0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Album ownership takeover in immich before 3.0.3 allows a user with shared-album editor access to escalate to full owner
Immich versions prior to 2.5.0 contain an improper access control flaw that allows any authenticated API key to escalate
Reflected cross-site scripting in Immich (commits 4ffa26c9 through pre-4eb1003) allows a single-click account takeover o
Authenticated partners in Immich through 3.3.1 can read metadata from assets stored in another user's Locked Folder - in
Remote code execution in Immich before 3.2.4 lets any authenticated non-admin user with upload permission run arbitrary
Locked asset visibility bypass in Immich through 3.1.0 exposes private photo and video assets to unauthorized viewers vi
Improper authorization in Immich's Shared Link Preview Handler (server/src/utils/access.ts, function checkSharedLinkAcce
Unauthenticated filesystem path injection in Immich's machine-learning service (vulnerable through 3.0.3, fixed in 3.3.0
Immich prior to version 2.6.0 discloses shared album passwords in cleartext within URL query parameters during authentic
Stored Cross-Site Scripting in Immich photo management platform versions prior to 2.7.0 enables authenticated attackers
Open redirect vulnerability in Immich prior to version 2.7.3 allows authenticated attackers to craft malicious shared al
Immich before 3.2.0 lets an authenticated regular user attach another user's asset to a shared link they legitimately ow
EUVD-2026-114376
NVD
CVE.org
EPSS
GitHub
Exploit-DB