CVE-2026-83803: Sentry RCE Vulnerability via Relocation

CVE-2026-83803 Overview

CVE-2026-83803 is an insecure deserialization vulnerability [CWE-502] in Sentry, the open-source error tracking and performance monitoring platform. Versions from 23.11.0 up to 26.7.0 unsafely deserialize a legacy database field when importing a user-supplied relocation archive. An authenticated user can craft a malicious archive that triggers arbitrary code execution in the import worker process. Sentry patched the flaw in version 26.7.0. Self-hosted installations running the default configuration are not affected because the relocation feature is disabled by default. Managed Sentry instances and self-hosted deployments that explicitly enabled relocation are exposed.

Critical Impact

Authenticated attackers can achieve arbitrary code execution inside Sentry's import worker process by uploading a crafted relocation archive.

Affected Products

• Sentry versions 23.11.0 through 26.6.x
• Sentry deployments with the relocation feature enabled
• Self-hosted Sentry instances that opted into relocation import workflows

Discovery Timeline

• 2026-09-22 - CVE-2026-83803 published to NVD
• 2026-09-22 - Last updated in NVD database

Technical Details for CVE-2026-83803

Vulnerability Analysis

Sentry's relocation feature lets users export and re-import organization data between instances as a signed archive. During import, the code path in src/sentry/backup/imports.py deserialized a legacy database field using Django's built-in serializers module. Because the payload originates from a user-uploaded archive, an authenticated attacker can substitute a malicious serialized object that executes code during reconstruction. Execution occurs inside the import worker process, which typically runs with elevated privileges relative to the tenant that submitted the archive. The attacker gains code execution in the Sentry backend, enabling lateral movement, credential theft from environment variables, and access to error telemetry that frequently includes sensitive customer data.

Root Cause

The root cause is insecure deserialization of an untrusted legacy field in the relocation import pipeline. The importer accepted serialized objects from the archive and instantiated them without validating type safety or restricting allowed classes. The fix removed the unsafe from django.core import serializers dependency and replaced the parsing path with orjson-based structured parsing, eliminating the object-reconstruction primitive.

Attack Vector

Exploitation requires authenticated access and permission to invoke the relocation import workflow. The attacker prepares a relocation archive containing a crafted legacy field payload. Uploading the archive to a vulnerable Sentry instance dispatches the import job to a worker, which deserializes the malicious payload and executes attacker-controlled code. No user interaction is required beyond the attacker's own upload.

# Patch excerpt: src/sentry/backup/imports.py
import orjson
from django.apps import apps
-from django.core import serializers
from django.core.exceptions import FieldDoesNotExist
from django.db import DatabaseError, connections, router, transaction
from sentry_sdk import capture_exception

Source: Sentry commit d7fd441. The removal of django.core.serializers eliminates the unsafe deserialization primitive; imports are now parsed via orjson structured JSON handling.

Detection Methods for CVE-2026-83803

Indicators of Compromise

• Unexpected relocation import jobs submitted by non-administrative users or from unusual source addresses.
• Sentry worker processes spawning child processes such as sh, bash, python, or outbound network utilities during or shortly after an import task.
• New or modified files in Sentry container filesystems that do not correspond to a known deployment.
• Outbound connections from Sentry worker containers to previously unseen destinations following archive uploads.

Detection Strategies

• Audit Sentry application logs for relocation import events and correlate with the initiating user, source IP, and archive size or hash.
• Instrument the import worker to log the classes and modules being deserialized during archive processing.
• Alert on anomalous process trees rooted in Sentry Celery workers, particularly interpreter or shell invocations.
• Compare the deployed Sentry version against 26.7.0 and flag any instance below that release with relocation enabled.

Monitoring Recommendations

• Forward Sentry container and worker telemetry to a centralized analytics platform for behavioral baselining.
• Monitor egress traffic from Sentry infrastructure for connections to non-approved destinations.
• Track authentication events for accounts with permission to submit relocation imports and alert on privilege changes.

How to Mitigate CVE-2026-83803

Immediate Actions Required

• Upgrade Sentry to version 26.7.0 or later, which removes the unsafe django.core.serializers code path.
• Disable the relocation feature until the upgrade is complete if you cannot patch immediately.
• Rotate any credentials, API tokens, and signing keys accessible to the Sentry worker environment if compromise is suspected.
• Review recent relocation import history and identify any archives submitted by non-trusted users.

Patch Information

Sentry addressed the vulnerability in release 26.7.0. Details are available in the Sentry GHSA-xm86-7c47-gjm4 advisory, the 26.7.0 release notes, and the remediation pull request. Operators of self-hosted Sentry should update container images or source checkouts to the fixed tag and redeploy import workers.

Workarounds

• Keep the relocation feature disabled, which is the default configuration for self-hosted deployments.
• Restrict access to relocation import endpoints via network policy or reverse-proxy rules until patched.
• Require administrator review and manual approval before processing any user-submitted relocation archive.

# Verify the running Sentry version and confirm the fix
sentry --version
# Expected: sentry, version 26.7.0 (or later)

# Confirm relocation is disabled in configuration
grep -Ei 'relocation' /etc/sentry/config.yml sentry.conf.py 2>/dev/null