OpAMP client reads unbounded HTTP response bodies_CVE-2026-42348

5.9 / 10

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Description

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 connection) and an extremely large body is returned in the response. This vulnerability is fixed in 0.2.0-alpha.1.

Basic Information

ID CVE-2026-42348

Source GitHub_M

Published May 12, 2026 at 18:01

Affected Product

Vendor open-telemetry

Product opentelemetry-dotnet-contrib

Version < 0.2.0-alpha.1

Affected Versions open-telemetry opentelemetry-dotnet-contrib < 0.2.0-alpha.1

CWE Classification

CWE-789

References

{
    "lastseen": "",
    "description": "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 connection) and an extremely large body is returned in the response. This vulnerability is fixed in 0.2.0-alpha.1.",
    "published": "2026-05-12T18:01:41.812Z",
    "modified": "2026-05-12T18:01:41.812Z",
    "type": "cve",
    "title": "OpAMP client reads unbounded HTTP response bodies",
    "source": "GitHub_M",
    "references": "https://github.com/open-telemetry/opentelemetry-dotnet-contrib/security/advisories/GHSA-w2jh-77fq-7gp8\nhttps://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4116",
    "id": "CVE-2026-42348",
    "bulletinFamily": "",
    "cwe": [
        "CWE-789"
    ],
    "cvelist": null,
    "sourceData": "open-telemetry opentelemetry-dotnet-contrib < 0.2.0-alpha.1",
    "sourceHref": "",
    "cvss": {
        "score": 5.9,
        "severity": "MEDIUM",
        "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
        "version": "3.1"
    },
    "cvss2": [],
    "cvss3": {
        "version": "",
        "vectorString": "",
        "baseScore": 0,
        "baseSeverity": "",
        "attackVector": "",
        "attackComplexity": "",
        "privilegesRequired": "",
        "userInteraction": "",
        "scope": "",
        "confidentialityImpact": "",
        "integrityImpact": "",
        "availabilityImpact": "",
        "cvssV3": {
            "version": "",
            "vectorString": "",
            "baseScore": 0,
            "baseSeverity": "",
            "attackVector": "",
            "attackComplexity": "",
            "privilegesRequired": "",
            "userInteraction": "",
            "scope": "",
            "confidentialityImpact": "",
            "integrityImpact": "",
            "availabilityImpact": ""
        }
    },
    "href": "",
    "category_name": "CVE",
    "post_link": "",
    "product": "opentelemetry-dotnet-contrib",
    "version": "< 0.2.0-alpha.1",
    "vendor": "open-telemetry",
    "ai_description": "",
    "ai_severity": "",
    "ai_vendor": "",
    "ai_product": "",
    "ai_version": "",
    "ai_score": 0
}