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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-83803 being exploited?
There is no known exploitation of CVE-2026-83803 in the wild and no public exploit code.
Sources
Also known as GHSA-xm86-7c47-gjm4.