# CVE-2026-83803: Sentry: Unsafe pickle deserialization in Relocation Feature

> Authenticated users can achieve arbitrary code execution in Sentry import workers via unsafe pickle deserialization when the optional relocation feature is enabled.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-xm86-7c47-gjm4

## What is CVE-2026-83803?

CVE-2026-83803 is a high-severity unsafe deserialization vulnerability in getsentry sentry, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-83803?


## How do I fix CVE-2026-83803?

No fix has been published for CVE-2026-83803 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-83803 being exploited?

There is no known exploitation of CVE-2026-83803 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-83803 and fix it if it is affected.

What it is: CVE-2026-83803 is a high-severity unsafe deserialization vulnerability in getsentry sentry, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-83803 in the wild and no public exploit code.

Affected product: getsentry sentry. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-83803/ (Markdown: https://insights.sbomify.com/CVE-2026-83803/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-83803
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-83803
- OSV: https://osv.dev/vulnerability/CVE-2026-83803

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-83803/
Summaries are generated and may contain mistakes; the official description above is the record.