VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sentry-sdk: vulnerability history, versions and safety

sentry-sdk is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 12 releases, from Mar 2023 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 L1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sentry-sdk vulnerabilities

Vulert verdict on sentry-sdk 2.73.0 i

Updated on 23 Oct 2026

Good news: 2.73.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 2.73.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.73.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.73.0 — unaffected i
  • Vulnerabilities on record 4 over 3 years · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.6 i
  • With no published fix 0 i
  • Stars 2,216 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for sentry-sdk, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.73.0 22 Oct 2026 none MIT — Details →
3.0.0b1 21 Oct 2026 none MIT — Details →
2.72.0 12 Oct 2026 none MIT — Details →
2.71.0 28 Sep 2026 none MIT — Details →
2.70.0 22 Sep 2026 none MIT — Details →
2.69.2 15 Sep 2026 none MIT — Details →
2.69.1 08 Sep 2026 none MIT — Details →
2.69.0 08 Sep 2026 none MIT — Details →
2.68.1 24 Aug 2026 none MIT — Details →
2.68.0 13 Aug 2026 none MIT — Details →
2.67.1 10 Aug 2026 none MIT — Details →
2.67.0 10 Aug 2026 none MIT — Details →
2.66.1 22 Jul 2026 none MIT — Details →
2.66.0 16 Jul 2026 none MIT — Details →
2.65.0 13 Jul 2026 none MIT — Details →
2.64.0 30 Jun 2026 none MIT — Details →
2.63.0 16 Jun 2026 none MIT — Details →
2.62.0 08 Jun 2026 none MIT — Details →
2.61.1 01 Jun 2026 none MIT — Details →
2.61.0 28 May 2026 none MIT — Details →
2.60.0 13 May 2026 none MIT — Details →
2.59.0a2 08 May 2026 none MIT — Details →
2.59.0a1 05 May 2026 none MIT — Details →
2.59.0 04 May 2026 none MIT — Details →
2.58.0a1 21 Apr 2026 none MIT — Details →
2.58.0 13 Apr 2026 none MIT — Details →
2.57.0 31 Mar 2026 none MIT — Details →
2.52.0a9 26 Mar 2026 none MIT — Details →
2.56.0 24 Mar 2026 none MIT — Details →
2.55.0 17 Mar 2026 none MIT — Details →
2.52.0a8 03 Mar 2026 none MIT — Details →
2.54.0 02 Mar 2026 none MIT — Details →
2.52.0a7 25 Feb 2026 none MIT — Details →
2.52.0a6 23 Feb 2026 none MIT — Details →
2.53.0 16 Feb 2026 none MIT — Details →
2.52.0a5 12 Feb 2026 none MIT — Details →
2.52.0a4 10 Feb 2026 none MIT — Details →
2.52.0a3 09 Feb 2026 none MIT — Details →
2.52.0 04 Feb 2026 none MIT — Details →
2.52.0a2 02 Feb 2026 none MIT — Details →
2.52.0a1 02 Feb 2026 none MIT — Details →
2.51.0 28 Jan 2026 none MIT — Details →
2.51.0a1 28 Jan 2026 none MIT — Details →
2.50.0 20 Jan 2026 none MIT — Details →
2.49.0 08 Jan 2026 none MIT — Details →
2.48.0 16 Dec 2025 none MIT — Details →
2.47.0 03 Dec 2025 none MIT — Details →
2.46.0 24 Nov 2025 none MIT — Details →
2.45.0 18 Nov 2025 none MIT — Details →
2.44.0 11 Nov 2025 none MIT — Details →
2.43.0 29 Oct 2025 none MIT — Details →
3.0.0a7 20 Oct 2025 none MIT — Details →
2.42.1 20 Oct 2025 none MIT — Details →
2.42.0 15 Oct 2025 none MIT — Details →
2.41.0 09 Oct 2025 none MIT — Details →
2.40.0 06 Oct 2025 none MIT — Details →
2.39.0 25 Sep 2025 none MIT — Details →
2.38.0 15 Sep 2025 none MIT — Details →
2.37.1 09 Sep 2025 none MIT — Details →
2.37.0 05 Sep 2025 none MIT — Details →
2.36.0 04 Sep 2025 none MIT — Details →
3.0.0a6 01 Sep 2025 none MIT — Details →
2.35.2 01 Sep 2025 none MIT — Details →
2.35.1 26 Aug 2025 none MIT — Details →
2.35.0 14 Aug 2025 none MIT — Details →
3.0.0a5 07 Aug 2025 none MIT — Details →
3.0.0a4 31 Jul 2025 none MIT — Details →
2.34.1 30 Jul 2025 none MIT — Details →
2.34.0 29 Jul 2025 none MIT — Details →
2.33.2 22 Jul 2025 none MIT — Details →
3.0.0a3 22 Jul 2025 none MIT — Details →
2.33.1 21 Jul 2025 none MIT — Details →
2.33.0 15 Jul 2025 none MIT — Details →
2.32.0 27 Jun 2025 none MIT — Details →
2.31.0 24 Jun 2025 none MIT — Details →
3.0.0a2 12 Jun 2025 none MIT — Details →
2.30.0 12 Jun 2025 none MIT — Details →
2.29.1 19 May 2025 none MIT — Details →
2.29.0 19 May 2025 none MIT — Details →
2.28.0 12 May 2025 none MIT — Details →
3.0.0a1 08 May 2025 none MIT — Details →
2.27.0 24 Apr 2025 none MIT — Details →
2.26.1 15 Apr 2025 none MIT — Details →
2.26.0 14 Apr 2025 none MIT — Details →
2.25.1 02 Apr 2025 none MIT — Details →
2.25.0 31 Mar 2025 none MIT — Details →
2.24.1 24 Mar 2025 none MIT — Details →
2.24.0 21 Mar 2025 none MIT — Details →
2.23.1 17 Mar 2025 none MIT — Details →
2.23.0 17 Mar 2025 none MIT — Details →
2.22.0 17 Feb 2025 none MIT — Details →
2.21.0 12 Feb 2025 none MIT — Details →
2.20.0 14 Jan 2025 none MIT — Details →
2.19.2 06 Dec 2024 none MIT — Details →
2.19.1 05 Dec 2024 none MIT — Details →
2.19.0 21 Nov 2024 none MIT — Details →
2.18.0 04 Nov 2024 none MIT — Details →
2.17.0 17 Oct 2024 none MIT — Details →
2.16.0 08 Oct 2024 none MIT — Details →
2.15.0 01 Oct 2024 none MIT — Details →
2.14.0 09 Sep 2024 none — — Details →
2.13.0 13 Aug 2024 none — — Details →
2.12.0 31 Jul 2024 none — — Details →
1.45.1 26 Jul 2024 none — — Details →
2.11.0 24 Jul 2024 none — — Details →
2.10.0 15 Jul 2024 none — — Details →
2.9.0 10 Jul 2024 none — — Details →
2.8.0 08 Jul 2024 none — — Details →
2.7.1 27 Jun 2024 L1 U1 — Yes Details →
2.7.0 26 Jun 2024 L1 U1 — Yes Details →
2.6.0 19 Jun 2024 L1 U1 — Yes Details →
2.5.1 07 Jun 2024 L1 U1 — Yes Details →
2.5.0 06 Jun 2024 L1 U1 — Yes Details →
2.4.0 04 Jun 2024 L1 U1 — Yes Details →
2.3.1 23 May 2024 L1 U1 — Yes Details →
2.3.0 23 May 2024 L1 U1 — Yes Details →
2.2.1 21 May 2024 L1 U1 — Yes Details →
2.2.0 16 May 2024 L1 U1 — Yes Details →
2.1.1 06 May 2024 L1 U1 — Yes Details →
2.1.0 06 May 2024 L1 U1 — Yes Details →

The newest 120 of 354 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for sentry-sdk

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-28117: Sentry SDK leaks sensitive session information in sentry-sdk 7.6 high 1.14.0 21 Mar 2023
CVE-2023-28117: Sentry SDK Session Information Leak Due to PII Exposure 7.6 high 1.14.0 07 Jul 2026
Unintentional Exposure of Environment Variables in Sentry's Python SDK 2.5 low 2.8.0 18 Jul 2024
CVE-2024-40647: Sentry SDK Python Environment Variable Exposure Vulnerability 2.5 low 1.45.1 07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About sentry-sdk

Is sentry-sdk safe to use?

Vulert records 4 vulnerabilities for sentry-sdk in PyPI: 0 critical, 1 high, 0 medium and 1 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is sentry-sdk's Vulert package health score?

Vulert scores sentry-sdk 81/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of sentry-sdk affected?

No. 2.73.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does sentry-sdk have?

4 vulnerabilities are recorded for sentry-sdk in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 1 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sentry-sdk vulnerabilities disclosed?

2 vulnerabilities were recorded for sentry-sdk in the last 12 months, and the oldest entry in this database dates to 21 Mar 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sentry-sdk are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor sentry-sdk for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sentry-sdk version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.