CVE-2026-42348: OpenTelemetry.OpAmp.Client is the OpAMP client for OpenTelemetry .NET

Q: How do I fix CVE-2026-42348?

opentelemetry.opamp.client: upgrade to 0.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-42348 being exploited?

CVE-2026-42348 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-42348 affect?

CVE-2026-42348 affects opentelemetry.opamp.client. Severity is medium (CVSS 5.9). OpenTelemetry.OpAmp.Client is the OpAMP client for OpenTelemetry .NET. Prior to 0.2.0-alpha.1, when receiving responses from the OpAMP server over HTTP, the OpAMP client allocates an unbounded buffer to read all bytes from the server, with

Q: How urgent is CVE-2026-42348?

Priority 32/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2026-42348 is a medium-severity flaw (CVSS 5.9) affecting opentelemetry.opamp.client. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

OpenTelemetry.OpAmp.Client is the OpAMP client for OpenTelemetry .NET. Prior to 0.2.0-alpha.1, when receiving responses from the OpAMP server over HTTP, the OpAMP client allocates an unbounded buffer to read all bytes from the server, with no upper-bound on the number of bytes consumed. This could cause memory exhaustion in the consuming application if the configured OpAMP server is attacker-controlled (or a network attacker can MitM the connecti

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-789
Published	2026-05-12
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: opentelemetry

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-12 18:17 UTCPublished CVE record published
2026-10-26 18:10 UTCUpdated Record last modified

opentelemetry opentelemetry.opamp.client UPGRADE

Affected: < 0.2.0

Fixed in: 0.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy opentelemetry.opamp.client || rpm -q opentelemetry.opamp.client || opentelemetry.opamp.client --version

2. UPGRADE to 0.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade opentelemetry.opamp.client

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade opentelemetry.opamp.client

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-42348?

opentelemetry.opamp.client: upgrade to 0.2.0. Exact commands for each OS are on this page.

Is CVE-2026-42348 being exploited?

CVE-2026-42348 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-42348 affect?

CVE-2026-42348 affects opentelemetry.opamp.client. Severity is medium (CVSS 5.9). OpenTelemetry.OpAmp.Client is the OpAMP client for OpenTelemetry .NET. Prior to 0.2.0-alpha.1, when receiving responses from the OpAMP server over HTTP, the OpAMP client allocates an unbounded buffer to read all bytes from the server, with

How urgent is CVE-2026-42348?

Priority 32/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs