CVE-2026-83803

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 22, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

26.7.0

Patch available: getsentry/sentry 26.7.0

https://github.com/getsentry/sentry/releases/tag/26.7.0
github_commit

commit d7fd44193c28 (getsentry/sentry)

Fix landed in getsentry/sentry commit d7fd44193c28 — awaiting tagged release

https://github.com/getsentry/sentry/commit/d7fd44193c282102f9fcd2c73973820f3d10ac3a
github_pr

chore: Improve relocation parsing efficiency.

Fix merged in getsentry/sentry PR #119622 on 2026-07-14 — awaiting tagged release

https://github.com/getsentry/sentry/pull/119622
github Patch Available

Unsafe pickle deserialization in Relocation Feature · Advisory · getsentry/sentry · GitHub

Affected: 26.7.0. The fix removes the serialization of the unsafe database field.

https://github.com/getsentry/sentry/security/advisories/GHSA-xm86-7c47-gjm4

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 15:52 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-24 04:32 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 18:33 UTCEG score recompute
  6. 2026-09-22 17:48 UTCEG score recompute
  7. 2026-09-22 17:34 UTCEG score recompute
  8. 2026-09-22 16:41 UTCEG score recompute
  9. 2026-09-22 16:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-83803?
CVE-2026-83803 is a high vulnerability published on September 22, 2026. 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…
When was CVE-2026-83803 disclosed?
CVE-2026-83803 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-83803 actively exploited?
CVE-2026-83803 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.4% of all scored CVEs.
What is the CVSS score of CVE-2026-83803?
CVE-2026-83803 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-83803?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83803, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-83803

Explore →

Is Your Infrastructure Affected by CVE-2026-83803?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs