VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Elastic.Apm: vulnerability history, versions and safety

Elastic.Apm is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 22 releases, first recorded in Nov 2023. 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 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all Elastic.Apm vulnerabilities

Vulert verdict on Elastic.Apm 1.35.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.35.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 22 Nov 2023 i
  • Highest CVSS 2.1 i
  • With no published fix 0 i
  • Stars 593 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by NuGet, 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 Elastic.Apm, 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.35.0 15 Sep 2026 none Apache-2.0 — Details →
1.34.7 04 Sep 2026 none Apache-2.0 — Details →
1.34.6 24 Aug 2026 none Apache-2.0 — Details →
1.34.5 29 Jun 2026 none Apache-2.0 — Details →
1.34.4 22 Jun 2026 none Apache-2.0 — Details →
1.34.3 11 Jun 2026 none Apache-2.0 — Details →
1.34.2 26 May 2026 none Apache-2.0 — Details →
1.34.1 12 Sep 2025 none Apache-2.0 — Details →
1.34.0 01 Sep 2025 none Apache-2.0 — Details →
1.33.0 19 Aug 2025 none Apache-2.0 — Details →
1.32.2 28 May 2025 none Apache-2.0 — Details →
1.31.0 02 Dec 2024 none Apache-2.0 — Details →
1.30.1 19 Nov 2024 none Apache-2.0 — Details →
1.30.0 11 Oct 2024 none Apache-2.0 — Details →
1.29.0 18 Sep 2024 none Apache-2.0 — Details →
1.25.3 08 Jan 2024 none non-standard — Details →
1.25.2 13 Dec 2023 none non-standard — Details →
1.25.1 21 Nov 2023 none non-standard — Details →
1.25.0 19 Oct 2023 none non-standard — Details →
1.24.0 20 Sep 2023 none non-standard — Details →
1.23.0 08 Aug 2023 none non-standard — Details →
1.22.0 28 Apr 2023 none non-standard — Details →
1.21.0 05 Apr 2023 none non-standard — Details →
1.20.0 27 Feb 2023 none non-standard — Details →
1.19.0 05 Dec 2022 none non-standard — Details →
1.18.0 13 Oct 2022 none non-standard — Details →
1.17.0 24 Aug 2022 none non-standard — Details →
1.16.1 14 Jun 2022 none non-standard — Details →
1.16.0 02 Jun 2022 none non-standard — Details →
1.15.0 12 May 2022 none non-standard — Details →
1.14.1 10 Mar 2022 none non-standard — Details →
1.14.0 09 Feb 2022 none non-standard — Details →
1.13.0 12 Jan 2022 none non-standard — Details →
1.12.1 15 Nov 2021 none non-standard — Details →
1.12.0 11 Nov 2021 none non-standard — Details →
1.11.1 13 Sep 2021 none non-standard — Details →
1.11.0 28 Jun 2021 none non-standard — Details →
1.10.0 27 May 2021 none non-standard — Details →
1.9.0 29 Mar 2021 L1 non-standard Yes Details →
1.8.1 25 Feb 2021 L1 non-standard Yes Details →
1.8.0 17 Feb 2021 L1 non-standard Yes Details →
1.7.1 30 Nov 2020 L1 non-standard Yes Details →
1.7.0 12 Nov 2020 L1 non-standard Yes Details →
1.6.1 20 Jul 2020 L1 non-standard Yes Details →
1.6.0 09 Jul 2020 L1 non-standard Yes Details →
1.5.1 14 May 2020 L1 non-standard Yes Details →
1.5.0 08 May 2020 L1 non-standard Yes Details →
1.4.0 20 Mar 2020 L1 non-standard Yes Details →
1.3.1 03 Mar 2020 L1 non-standard Yes Details →
1.3.0 12 Feb 2020 L1 non-standard Yes Details →
1.2.0 22 Nov 2019 L1 non-standard Yes Details →
1.1.2 11 Oct 2019 L1 non-standard Yes Details →
1.1.1 03 Oct 2019 L1 non-standard Yes Details →
1.1.0 01 Oct 2019 L1 non-standard Yes Details →
1.0.1 26 Aug 2019 L1 non-standard Yes Details →
1.0.0 31 Jul 2019 L1 non-standard Yes Details →
1.0.0-beta1 18 Jun 2019 L1 non-standard Yes Details →
0.0.2-alpha 27 Mar 2019 L1 non-standard Yes Details →
0.0.1-alpha 07 Feb 2019 L1 non-standard Yes Details →
0.0.1 — L1 non-standard Yes Details →
1.26.0 — none Apache-2.0 — Details →
1.27.0 — none Apache-2.0 — Details →
1.27.1 — none Apache-2.0 — Details →
1.27.2 — none Apache-2.0 — Details →
1.27.3 — none Apache-2.0 — Details →
1.28.0 — none Apache-2.0 — Details →
1.28.1 — none Apache-2.0 — Details →
1.28.2 — none Apache-2.0 — Details →
1.28.3 — none Apache-2.0 — Details →
1.28.4 — none Apache-2.0 — Details →
1.28.5 — none Apache-2.0 — Details →
1.28.6 — none Apache-2.0 — Details →

All 72 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

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

03 Vulnerabilities

Recorded vulnerabilities for Elastic.Apm

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Exposure of Sensitive Information in Elastic APM .NET Agent 2.1 low 1.10.0 22 Nov 2023

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 Elastic.Apm

Is Elastic.Apm safe to use?

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

Vulert scores Elastic.Apm 85/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 Elastic.Apm affected?

No. 1.35.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.

Which version of Elastic.Apm should I use?

1.35.0 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 Elastic.Apm have?

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

How often are new Elastic.Apm vulnerabilities disclosed?

0 vulnerabilities were recorded for Elastic.Apm in the last 12 months, and the oldest entry in this database dates to 22 Nov 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 Elastic.Apm 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 Elastic.Apm for upcoming vulnerabilities?

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