Description
Sentry is an error tracking and performance monitoring tool. From 23.11.0 until 26.7.0, Sentry instances with the relocation feature enabled unsafely deserialize a legacy database field while importing a user-supplied relocation archive. An authenticated user can craft an archive that causes arbitrary code execution in the import worker process. Self-hosted installations using the default configuration are not affected because the relocation feature is disabled by default. This issue is fixed in version 26.7.0.
Published: 2026-09-22
Score: 7.7 High
EPSS: n/a
KEV: No
Impact: Remote code execution
Action: Immediate Patch
AI Analysis

Impact

An insecure deserialization of Python pickle objects occurs when Sentry imports a user‑supplied relocation archive. The import worker process will execute the contained objects, allowing an authenticated attacker to run arbitrary code on the host. This can lead to full system compromise because the worker operates with the privileged credentials of the Sentry instance.

Affected Systems

The affected vendor is Sentry by Getsentry. Any instance running version 23.11.0 through 26.6.x with the relocation feature enabled is vulnerable. Self‑hosted installations in the default configuration are safe because the relocation feature is disabled by default, but any manual enablement places the instance at risk.

Risk and Exploitability

The CVSS score of 7.7 classifies the vulnerability as high severity. No EPSS data is available and the issue is not listed in the CISA KEV catalog. Exploitation requires an authenticated user who can trigger an import of a malicious relocation archive. The attack vector is therefore likely an authenticated API or UI operation, and the attacker can execute arbitrary code on the host through the import worker process.

Generated by OpenCVE AI on September 22, 2026 at 17:36 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Sentry to version 26.7.0 or later
  • If upgrading is not immediately possible, disable the relocation feature in the Sentry configuration to prevent deserialization of legacy archives
  • Limit user privileges for importing relocation archives or monitor for abnormal import activity to detect potential malicious uploads

Generated by OpenCVE AI on September 22, 2026 at 17:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 22 Sep 2026 17:45:00 +0000

Type Values Removed Values Added
First Time appeared Getsentry
Getsentry sentry
Vendors & Products Getsentry
Getsentry sentry

Tue, 22 Sep 2026 16:45:00 +0000

Type Values Removed Values Added
Description Sentry is an error tracking and performance monitoring tool. From 23.11.0 until 26.7.0, Sentry instances with the relocation feature enabled unsafely deserialize a legacy database field while importing a user-supplied relocation archive. An authenticated user can craft an archive that causes arbitrary code execution in the import worker process. Self-hosted installations using the default configuration are not affected because the relocation feature is disabled by default. This issue is fixed in version 26.7.0.
Title Sentry: Unsafe pickle deserialization in Relocation Feature
Weaknesses CWE-502
References
Metrics cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Getsentry Sentry
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-22T17:43:35.934Z

Reserved: 2026-08-31T23:04:48.172Z

Link: CVE-2026-83803

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-22T17:17:26.710

Modified: 2026-09-22T17:17:26.710

Link: CVE-2026-83803

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-22T17:30:18Z

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data