Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-41484 medium CVSS 5.3

Vulnerability in OpenTelemetry.Exporter.OneCollector (CVE-2026-41484)

Summary

Vulnerability in OpenTelemetry.Exporter.OneCollector (CVE-2026-41484). Risk of unauthorized operations or information disclosure. Exploitable via HttpJsonPostTransport. Mitigation: upgrade to 1.15.1 or later.

Original description

The description as published by the source.

Summary

When exporting telemetry to a back-end/collector over HTTP using the OpenTelemetry.Exporter.OneCollector exporter, if the request results in a unsuccessful request (i.e. HTTP 4xx or 5xx), the response is read into memory with no upper-bound on the number of bytes consumed.

This could cause memory exhaustion in the consuming application if the configured back-end/collector endpoint is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned by the response.

Details

The HttpJsonPostTransport class reads the response body when a non-200 HTTP status code is received when exporting telemetry to aid debugging by operators so that the error response is included in the logs emitted by the exporter.

An attacker who controls the configured endpoint, or who can intercept traffic to them (MiTM), can return an arbitrarily large response body. This causes unbounded heap allocation in the consuming process, leading to high transient memory pressure, garbage-collection stalls, or an OutOfMemoryException that terminates the process.

Impact

If an application using the OneCollector exporter is configured to use a back-end/collector endpoint that is attacker-controlled (or a network attacker can MitM the connection) and an…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41484 has been found in OpenTelemetry.Exporter.OneCollector.
Attackers can target a specific entry point like HttpJsonPostTransport over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade OpenTelemetry.Exporter.OneCollector to 1.15.1 or later.
If unsure, ask your IT team or search "OpenTelemetry.Exporter.OneCollector CVE-2026-41484" on the vendor's site.

CVE-2026-41484 (OpenTelemetry.Exporter.OneCollector) — CWE-770 / CVSS v3 5.3
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: HttpJsonPostTransport
Patched: 1.15.1 — apply immediately
Workaround: Use network-level controls (firewall rules, mTLS, service mesh) to prevent Man-in-the-Middle (MitM) attacks on the configured back-end/collector endpoint.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-770) exists in OpenTelemetry.Exporter.OneCollector. Attackers reach the vulnerable code path via HttpJsonPostTransport without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of OpenTelemetry.Exporter.OneCollector. Attack surface: HttpJsonPostTransport.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.15.1.

🛡️ Workaround

Workaround: Use network-level controls (firewall rules, mTLS, service mesh) to prevent Man-in-the-Middle (MitM) attacks on the configured back-end/collector endpoint.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'OpenTelemetry.Exporter.OneCollector' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'OpenTelemetry.Exporter.OneCollector' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で OpenTelemetry.Exporter.OneCollector を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Use network-level controls (firewall rules, mTLS, service mesh) to prevent Man-in-the-Middle (MitM) attacks on the configured back-end/collector endpoint.

    パッチが適用されるまでの応急処置として、Use network-level controls (firewall rules, mTLS, service mesh) to prevent Man-in-the-Middle (MitM) attacks on the configured back-end/collector endpoint. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade OpenTelemetry.Exporter.OneCollector to 1.15.1

    ステージング環境で 1.15.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget OpenTelemetry.Exporter.OneCollector
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.15.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details