VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

opentelemetry-instrumentation: vulnerability history, versions and safety

opentelemetry-instrumentation is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 39 releases, from Oct 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
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 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 opentelemetry-instrumentation vulnerabilities

Vulert verdict on opentelemetry-instrumentation 0.66.0b1 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.66.0b1 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 3,123 packages i
  • Stars 1,119 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 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 opentelemetry-instrumentation, 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
0.66.0b1 06 Oct 2026 none Apache-2.0 — Details →
0.66.0b0 25 Sep 2026 none Apache-2.0 — Details →
0.65.0b0 16 Jul 2026 none Apache-2.0 — Details →
0.64.0b0 24 Jun 2026 none Apache-2.0 — Details →
0.63.0b1 21 May 2026 none Apache-2.0 — Details →
0.63.0b0 19 May 2026 none Apache-2.0 — Details →
0.62.0b1 24 Apr 2026 none Apache-2.0 — Details →
0.62.0b0 09 Apr 2026 none Apache-2.0 — Details →
0.61.0b0 04 Mar 2026 none Apache-2.0 — Details →
0.60.0b1 11 Dec 2025 none Apache-2.0 — Details →
0.60.0b0 03 Dec 2025 none Apache-2.0 — Details →
0.59.0b0 16 Oct 2025 none Apache-2.0 — Details →
0.58.0b0 11 Sep 2025 none Apache-2.0 — Details →
0.57.0b0 29 Jul 2025 none Apache-2.0 — Details →
0.56.0b0 11 Jul 2025 none Apache-2.0 — Details →
0.55.0b1 10 Jun 2025 none Apache-2.0 — Details →
0.55.0b0 04 Jun 2025 none Apache-2.0 — Details →
0.54.0b1 16 May 2025 none Apache-2.0 — Details →
0.54.0b0 09 May 2025 none Apache-2.0 — Details →
0.53.0b1 15 Apr 2025 none Apache-2.0 — Details →
0.53.0b0 10 Apr 2025 none Apache-2.0 — Details →
0.52.0b1 20 Mar 2025 none Apache-2.0 — Details →
0.52.0b0 12 Mar 2025 none Apache-2.0 — Details →
0.51.0b0 04 Feb 2025 none Apache-2.0 — Details →
0.50.0b0 11 Dec 2024 none Apache-2.0 — Details →
0.49.0b2 18 Nov 2024 none Apache-2.0 — Details →
0.49.0b1 08 Nov 2024 none Apache-2.0 — Details →
0.49.0b0 05 Nov 2024 none Apache-2.0 — Details →
0.48.0b0 28 Aug 2024 none Apache-2.0 — Details →
0.47.0b0 25 Jul 2024 none Apache-2.0 — Details →
0.46.0b0 31 May 2024 none Apache-2.0 — Details →
0.45.0b0 28 Mar 2024 none Apache-2.0 — Details →
0.44.0b0 23 Feb 2024 none Apache-2.0 — Details →
0.43.0b0 15 Dec 2023 none Apache-2.0 — Details →
0.42.0b0 08 Nov 2023 none Apache-2.0 — Details →
0.41.0b0 11 Sep 2023 none Apache-2.0 — Details →
0.40.0b0 13 Jul 2023 H1 U1 Apache-2.0 Yes Details →
0.39.0b0 19 May 2023 H1 U1 Apache-2.0 Yes Details →
0.38.0b0 22 Mar 2023 H1 U1 Apache-2.0 Yes Details →
0.37.0b0 17 Feb 2023 H1 U1 Apache-2.0 Yes Details →
0.36.0b0 09 Dec 2022 H1 U1 non-standard Yes Details →
0.35.0b0 03 Nov 2022 H1 U1 non-standard Yes Details →
0.34.0b0 27 Sep 2022 H1 U1 non-standard Yes Details →
0.33.0b0 09 Aug 2022 H1 U1 Apache-2.0 Yes Details →
0.32.0b0 04 Jul 2022 H1 U1 Apache-2.0 Yes Details →
0.31.0b0 17 May 2022 H1 U1 Apache-2.0 Yes Details →
0.30.0b1 21 Apr 2022 H1 U1 Apache-2.0 Yes Details →
0.30.0b0 18 Apr 2022 H1 U1 Apache-2.0 Yes Details →
0.29.0b0 11 Mar 2022 H1 U1 Apache-2.0 Yes Details →
0.28.0b1 31 Jan 2022 H1 U1 Apache-2.0 Yes Details →
0.28.0b0 26 Jan 2022 H1 U1 Apache-2.0 Yes Details →
0.27.0b0 17 Dec 2021 H1 U1 Apache-2.0 Yes Details →
0.26.0b1 11 Nov 2021 H1 U1 Apache-2.0 Yes Details →
0.25.0b2 19 Oct 2021 H1 U1 Apache-2.0 Yes Details →
0.25.0b1 18 Oct 2021 H1 U1 Apache-2.0 Yes Details →
0.25.0b0 13 Oct 2021 H1 U1 Apache-2.0 Yes Details →
0.24.0b0 26 Aug 2021 H1 U1 Apache-2.0 Yes Details →
0.23.0b2 28 Jul 2021 H1 U1 Apache-2.0 Yes Details →
0.23.0b1 26 Jul 2021 H1 U1 Apache-2.0 Yes Details →
0.23.0b0 21 Jul 2021 H1 U1 Apache-2.0 Yes Details →
0.22.0b0 02 Jun 2021 H1 U1 Apache-2.0 Yes Details →
0.21.0b0 12 May 2021 H1 U1 Apache-2.0 Yes Details →
0.20.0b0 20 Apr 2021 H1 U1 Apache-2.0 Yes Details →
0.19.0b0 26 Mar 2021 H1 U1 Apache-2.0 Yes Details →
0.18.0b0 16 Feb 2021 H1 U1 Apache-2.0 Yes Details →
0.17.0b0 20 Jan 2021 H1 U1 Apache-2.0 Yes Details →
0.16.0b1 27 Nov 2020 H1 U1 Apache-2.0 Yes Details →
0.16.0b0 26 Nov 2020 H1 U1 Apache-2.0 Yes Details →
0.15.0b0 02 Nov 2020 H1 U1 Apache-2.0 Yes Details →
0.14.0b0 13 Oct 2020 H1 U1 Apache-2.0 Yes Details →
0.13.0b0 17 Sep 2020 H1 U1 Apache-2.0 Yes Details →
0.12.0b0 14 Aug 2020 H1 U1 Apache-2.0 Yes Details →
0.11.0b0 28 Jul 2020 H1 U1 Apache-2.0 Yes Details →
0.10.0b0 23 Jun 2020 H1 U1 Apache-2.0 Yes Details →
0.9.0b0 11 Jun 2020 H1 U1 Apache-2.0 Yes Details →

All 75 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for opentelemetry-instrumentation

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in opentelemetry-instrumentation 7.5 high 0.41b0 02 Oct 2023
CVE-2023-43810: opentelemetry-instrumentation Denial of Service Vulnerability Due to Unbound Cardinality Metrics 7.5 high 0.41b0 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 opentelemetry-instrumentation

Is opentelemetry-instrumentation safe to use?

Vulert records 2 vulnerabilities for opentelemetry-instrumentation in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 opentelemetry-instrumentation's Vulert package health score?

Vulert scores opentelemetry-instrumentation 84/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 opentelemetry-instrumentation affected?

No. 0.66.0b1, 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.

Which version of opentelemetry-instrumentation should I use?

0.66.0b1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does opentelemetry-instrumentation have?

2 vulnerabilities are recorded for opentelemetry-instrumentation in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 opentelemetry-instrumentation vulnerabilities disclosed?

1 vulnerability was recorded for opentelemetry-instrumentation in the last 12 months, and the oldest entry in this database dates to 02 Oct 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 opentelemetry-instrumentation 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 opentelemetry-instrumentation for upcoming vulnerabilities?

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