Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

opentelemetry.opamp.client

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.9NuGetPublished

    OpAMP client reads unbounded HTTP response bodies

    CVE-2026-42348 · GHSA-w2jh-77fq-7gp8

    Affected
    • NuGet opentelemetry.opamp.client < 0.2.0-alpha.1
    Fixed in
    0.2.0-alpha.1· Vendor fix available
    Issue
    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 connection) and an extremely large body is returned in the response. Details #2926 introduced the initial HTTP transport components which uses ReadAsByteArrayAsync to copy the HttpResponseMessage.Content into a byte array. This code path allows an unbounded read of the entire HTTP response message. Impact If an application using the OpAMP client is configured to use an OpAMP server that is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned in the response, the application could have its memory exhausted and create a denial-of-service condition. Mitigation The application's…

    Recommended action: Upgrade to 0.2.0-alpha.1 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →