GHSA-hv27-723h-qfjq: Immich: Partner "view-only" sharing leaks GPS coordinates of the sharer's archived assets via GET /api/map/markers

Published Oct 30, 2026
·
Updated

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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Immich to a version that resolves this vulnerability.

    Fixed in 3.0.0

Event History

Oct 30, 2026
CVE Published
via OSV·07:51 PM
Data Sourced
via OSV·07:51 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

A user configured as a view-only partner of another Immich user can exploit it. The affected data belongs to the sharing partner and is limited to that partner's archived assets.

2

What access and request conditions are required?

The attacker needs authenticated view-only partner access and must query GET /api/map/markers with withPartners=true for archived assets. No user interaction is required.

3

What information is exposed?

The issue exposes GPS coordinates and asset identifiers, as well as the existence of archived photos or videos. Image and video bytes remain protected by checkPartnerAccess.

4

Are deployments affected by default?

The issue depends on a view-only partner relationship and use of the map markers endpoint with partner results enabled. The provided information does not establish that every default deployment has such relationships configured.

5

What version fixes the issue?

Upgrade Immich to version 3.0.0 or later. Versions prior to 3.0.0 are affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203