Security readout for executives and security teams
Plain-English summary
Immich versions before 2.5.0 let an existing API key upgrade its own permissions. A key that should have limited access could become an administrator, exposing photos, videos, users, and system settings. This requires possession of an API key, but the business impact is high if keys are leaked, shared, or over-issued.
Executive priority
Prioritize within the normal high-severity patch window, faster for internet-exposed or multi-user Immich deployments. The issue can turn limited API access into full administrative access, making API key hygiene and prompt upgrade important.
Technical view
CVE-2026-23896 is a CWE-269 privilege escalation in immich. Before version 2.5.0, API keys could call the update endpoint to grant themselves full administrative permissions. CVSS 3.1 is 7.2, with network access, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Self-hosted Immich deployments running versions earlier than 2.5.0 are affected. Exposure is most relevant where API keys exist, especially keys assigned limited permissions, stored in integrations, or accessible to users, services, or automation.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation. Exploitation requires an attacker already having a valid API key. If obtained, the flaw can convert limited API access into administrative control.
Researcher notes
Evidence is limited to the CVE record and GitHub advisory. The advisory states the root issue and fixed version but no exploit activity is cited. Avoid assuming broader product impact beyond immich versions before 2.5.0.
Mitigation direction
- Upgrade Immich to version 2.5.0 or later.
- Review vendor advisory GHSA-237r-x578-h5mv for current guidance.
- Rotate API keys that may have been exposed or broadly distributed.
- Reduce API key issuance and remove keys no longer needed.
- Review administrative users and permissions after upgrading.
Validation and detection
- Inventory all Immich instances and record their versions.
- Confirm every instance is running Immich 2.5.0 or later.
- Review API keys for unexpected administrative permissions.
- Check audit logs for unusual API key permission changes, if available.
- Verify integrations still use least-privilege API keys.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23896 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/immich-app/immich/security/advisories/GHSA-237r-x578-h5mvCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.