VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

opentelemetry-api: vulnerability history, versions and safety

opentelemetry-api is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 85 releases, first recorded in Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all opentelemetry-api vulnerabilities

Vulert verdict on opentelemetry-api 1.45.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.45.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 62,436 packages i
  • Stars 2,685 i
  • OpenSSF scorecard 7/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-api, 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
1.45.1 06 Oct 2026 none Apache-2.0 — Details →
1.45.0 25 Sep 2026 M1 Apache-2.0 Yes Details →
1.44.0 16 Jul 2026 M1 Apache-2.0 Yes Details →
1.43.0 24 Jun 2026 M1 Apache-2.0 Yes Details →
1.42.1 21 May 2026 M1 Apache-2.0 Yes Details →
1.42.0 19 May 2026 M1 Apache-2.0 Yes Details →
1.41.1 24 Apr 2026 M1 Apache-2.0 Yes Details →
1.41.0 09 Apr 2026 M1 Apache-2.0 Yes Details →
1.40.0 04 Mar 2026 M1 Apache-2.0 Yes Details →
1.39.1 11 Dec 2025 M1 Apache-2.0 Yes Details →
1.39.0 03 Dec 2025 M1 Apache-2.0 Yes Details →
1.38.0 16 Oct 2025 M1 Apache-2.0 Yes Details →
1.37.0 11 Sep 2025 M1 Apache-2.0 Yes Details →
1.36.0 29 Jul 2025 M1 Apache-2.0 Yes Details →
1.35.0 11 Jul 2025 M1 Apache-2.0 Yes Details →
1.34.1 10 Jun 2025 M1 Apache-2.0 Yes Details →
1.34.0 04 Jun 2025 M1 Apache-2.0 Yes Details →
1.33.1 16 May 2025 M1 Apache-2.0 Yes Details →
1.33.0 09 May 2025 M1 Apache-2.0 Yes Details →
1.32.1 15 Apr 2025 M1 Apache-2.0 Yes Details →
1.32.0 10 Apr 2025 M1 Apache-2.0 Yes Details →
1.31.1 20 Mar 2025 M1 Apache-2.0 Yes Details →
1.31.0 12 Mar 2025 M1 Apache-2.0 Yes Details →
1.30.0 04 Feb 2025 M1 Apache-2.0 Yes Details →
1.29.0 11 Dec 2024 M1 Apache-2.0 Yes Details →
1.28.2 18 Nov 2024 M1 Apache-2.0 Yes Details →
1.28.1 08 Nov 2024 M1 Apache-2.0 Yes Details →
1.28.0 05 Nov 2024 M1 Apache-2.0 Yes Details →
1.27.0 28 Aug 2024 M1 Apache-2.0 Yes Details →
1.26.0 25 Jul 2024 M1 Apache-2.0 Yes Details →
1.25.0 31 May 2024 M1 Apache-2.0 Yes Details →
1.24.0 28 Mar 2024 M1 Apache-2.0 Yes Details →
1.23.0 23 Feb 2024 M1 Apache-2.0 Yes Details →
1.22.0 15 Dec 2023 M1 Apache-2.0 Yes Details →
1.21.0 07 Nov 2023 M1 Apache-2.0 Yes Details →
1.20.0 04 Sep 2023 M1 Apache-2.0 Yes Details →
1.19.0 13 Jul 2023 M1 Apache-2.0 Yes Details →
1.18.0 19 May 2023 M1 Apache-2.0 Yes Details →
1.17.0 22 Mar 2023 M1 Apache-2.0 Yes Details →
1.16.0 17 Feb 2023 M1 Apache-2.0 Yes Details →
1.15.0 09 Dec 2022 M1 non-standard Yes Details →
1.14.0 03 Nov 2022 M1 non-standard Yes Details →
1.13.0 26 Sep 2022 M1 non-standard Yes Details →
1.12.0 09 Aug 2022 M1 Apache-2.0 Yes Details →
1.12.0rc2 04 Jul 2022 M1 Apache-2.0 Yes Details →
1.12.0rc1 17 May 2022 M1 Apache-2.0 Yes Details →
1.11.1 21 Apr 2022 M1 Apache-2.0 Yes Details →
1.11.0 18 Apr 2022 M1 Apache-2.0 Yes Details →
1.10.0 11 Mar 2022 M1 Apache-2.0 Yes Details →
1.9.1 31 Jan 2022 M1 Apache-2.0 Yes Details →
1.9.0 26 Jan 2022 M1 Apache-2.0 Yes Details →
1.8.0 17 Dec 2021 M1 Apache-2.0 Yes Details →
1.7.1 11 Nov 2021 M1 Apache-2.0 Yes Details →
1.7.0 11 Nov 2021 M1 Apache-2.0 Yes Details →
1.6.2 19 Oct 2021 M1 Apache-2.0 Yes Details →
1.6.1 18 Oct 2021 M1 Apache-2.0 Yes Details →
1.6.0 13 Oct 2021 M1 Apache-2.0 Yes Details →
1.5.0 26 Aug 2021 M1 Apache-2.0 Yes Details →
1.4.1 28 Jul 2021 M1 Apache-2.0 Yes Details →
1.4.0 21 Jul 2021 M1 Apache-2.0 Yes Details →
1.3.0 02 Jun 2021 M1 Apache-2.0 Yes Details →
1.2.0 12 May 2021 M1 Apache-2.0 Yes Details →
1.1.0 20 Apr 2021 M1 Apache-2.0 Yes Details →
1.10.0a0 07 Apr 2021 M1 Apache-2.0 Yes Details →
1.0.0 26 Mar 2021 M1 Apache-2.0 Yes Details →
1.0.0rc1 12 Feb 2021 M1 Apache-2.0 Yes Details →
0.17.0b0 20 Jan 2021 M1 Apache-2.0 Yes Details →
0.16.0b1 27 Nov 2020 M1 Apache-2.0 Yes Details →
0.16.0b0 26 Nov 2020 M1 Apache-2.0 Yes Details →
0.15.0b0 02 Nov 2020 M1 Apache-2.0 Yes Details →
0.14.0b0 13 Oct 2020 M1 Apache-2.0 Yes Details →
0.13.0b0 17 Sep 2020 M1 Apache-2.0 Yes Details →
0.12.0b0 14 Aug 2020 M1 Apache-2.0 Yes Details →
0.11.0b0 28 Jul 2020 M1 Apache-2.0 Yes Details →
0.10.0b0 23 Jun 2020 M1 Apache-2.0 Yes Details →
0.9.0b0 11 Jun 2020 M1 Apache-2.0 Yes Details →
0.8.0b0 27 May 2020 M1 Apache-2.0 Yes Details →
0.7.0b1 13 May 2020 M1 Apache-2.0 Yes Details →
0.7.0b0 12 May 2020 M1 Apache-2.0 Yes Details →
0.6.0b0 31 Mar 2020 M1 Apache-2.0 Yes Details →
0.5.0b0 16 Mar 2020 M1 Apache-2.0 Yes Details →
0.4.0a1 04 Mar 2020 M1 Apache-2.0 Yes Details →
0.4.0a0 21 Feb 2020 M1 Apache-2.0 Yes Details →
0.3.0a0 12 Dec 2019 M1 Apache-2.0 Yes Details →
0.2.0a0 30 Oct 2019 M1 Apache-2.0 Yes Details →
0.1.0a0 01 Oct 2019 M1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for opentelemetry-api

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-114603: Excessive CPU use when parsing OpenTelemetry tracestate headers 5.3 medium 1.45.1 22 Oct 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-api

Is opentelemetry-api safe to use?

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

Vulert scores opentelemetry-api 91/100, which reads as healthy. 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-api affected?

No. 1.45.1, 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-api should I use?

1.45.1 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-api have?

1 vulnerability is recorded for opentelemetry-api in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new opentelemetry-api vulnerabilities disclosed?

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

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