opentelemetry_exporter_otlp-1.40.0-py3-none-any.whl: 3 vulnerabilities (highest severity is: 6.5)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 77/100
Research direction
Start with examples/trace-analytics-sample-app/sample-app/requirements.txt, the dependency file named in the report. Review the OpenTelemetry exporter version and its dependency constraints, then check the sample app's setup instructions for how dependencies are installed. Done when the dependency versions resolve to releases that include the reported fixes for all three vulnerabilities.
Written by the indexing model from the issue text.
Description
Vulnerable Library - opentelemetry_exporter_otlp-1.40.0-py3-none-any.whl
Sample Path to Dependency File: /examples/trace-analytics-sample-app/sample-app/requirements.txt
Path to vulnerable library: /tmp/ws-ua_20261120230458_JTRJRK/python_QLMXBQ/202611202304591/site-packages-1/opentelemetry_exporter_otlp_proto_http-1.40.0.dist-info
Found in HEAD commit: aff23afca7be6eb37ce42d1448e445bc8b72b853
Vulnerabilities
| Vulnerability | Severity | CVSS |
Dependency | Type | Fixed in (opentelemetry_exporter_otlp version) | Remediation Possible** |
|---|---|---|---|---|---|---|
| CVE-2026-112006 | Medium |
6.5 | opentelemetry_exporter_otlp_proto_http-1.40.0-py3-none-any.whl | Transitive | 1.41.0 | ✅ |
| CVE-2026-126360 | Medium |
5.3 | opentelemetry_api-1.40.0-py3-none-any.whl | Transitive | 1.45.0 | ✅ |
| CVE-2026-114603 | Medium |
5.3 | opentelemetry_api-1.40.0-py3-none-any.whl | Transitive | 1.45.0 | ✅ |
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2026-112006
Vulnerable Library - opentelemetry_exporter_otlp_proto_http-1.40.0-py3-none-any.whl
OpenTelemetry Collector Protobuf over HTTP Exporter
Library home page: https://files.pythonhosted.org/packages/a0/3a/8865d6754e61c9fb170cdd530a124a53769ee5f740236064816eb0ca7301/opentelemetry_exporter_otlp_proto_http-1.40.0-py3-none-any.whl
Sample Path to Dependency File: /examples/trace-analytics-sample-app/sample-app/requirements.txt
Path to vulnerable library: /tmp/ws-ua_20261120230458_JTRJRK/python_QLMXBQ/202611202304591/site-packages-1/opentelemetry_exporter_otlp_proto_http-1.40.0.dist-info
Dependency Hierarchy:
- opentelemetry_exporter_otlp-1.40.0-py3-none-any.whl (Root Library)
- ❌ opentelemetry_exporter_otlp_proto_http-1.40.0-py3-none-any.whl (Vulnerable Library)
Found in HEAD commit: aff23afca7be6eb37ce42d1448e445bc8b72b853
Found in base branch: main
Vulnerability Details
OpenTelemetry opentelemetry-exporter-otlp-proto-http 1.5.0 before 1.45.0 contains an improper certificate validation vulnerability that disables TLS verification when OTEL_EXPORTER_OTLP_CERTIFICATE variables are empty strings. Man-in-the-middle attackers can impersonate the collector to read or alter exported traces, metrics, and logs, including authentication headers from OTEL_EXPORTER_OTLP_HEADERS.
Publish Date: 2026-10-18
URL: CVE-2026-112006
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Release Date: 2026-10-18
Fix Resolution (opentelemetry-exporter-otlp-proto-http): 1.45.0
Direct dependency fix Resolution (opentelemetry-exporter-otlp): 1.41.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2026-126360
Vulnerable Library - opentelemetry_api-1.40.0-py3-none-any.whl
OpenTelemetry Python API
Library home page: https://files.pythonhosted.org/packages/5f/bf/93795954016c522008da367da292adceed71cca6ee1717e1d64c83089099/opentelemetry_api-1.40.0-py3-none-any.whl
Sample Path to Dependency File: /examples/trace-analytics-sample-app/sample-app/requirements.txt
Path to vulnerable library: /tmp/ws-ua_20261120230458_JTRJRK/python_QLMXBQ/202611202304591/site-packages-1/opentelemetry_api-1.40.0.dist-info
Dependency Hierarchy:
- opentelemetry_exporter_otlp-1.40.0-py3-none-any.whl (Root Library)
- opentelemetry_exporter_otlp_proto_grpc-1.40.0-py3-none-any.whl
- ❌ opentelemetry_api-1.40.0-py3-none-any.whl (Vulnerable Library)
- opentelemetry_exporter_otlp_proto_grpc-1.40.0-py3-none-any.whl
Found in HEAD commit: aff23afca7be6eb37ce42d1448e445bc8b72b853
Found in base branch: main
Vulnerability Details
OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.2, TraceContextTextMapPropagator.extract() in opentelemetry-api can perform quadratic-time regular-expression backtracking on a malformed traceparent value containing a trace-context prefix, a long whitespace sequence, and an embedded newline. Exploitation requires an attacker-controlled carrier that preserves embedded newlines and permits a sufficiently large value, because conforming HTTP header values cannot contain embedded newlines. JSON-based carriers, including applicable MCP request metadata integrations, can preserve the required newline depending on the SDK, instrumentation, and message-size limits. Parsing on an asynchronous server's event-loop thread can consume excessive CPU and delay unrelated requests, while the advisory does not establish disclosure, modification, or code execution. This issue is fixed in version 1.45.2.
Publish Date: 2026-11-12
URL: CVE-2026-126360
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Release Date: 2026-11-12
Fix Resolution (opentelemetry-api): 1.45.2
Direct dependency fix Resolution (opentelemetry-exporter-otlp): 1.45.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2026-114603
Vulnerable Library - opentelemetry_api-1.40.0-py3-none-any.whl
OpenTelemetry Python API
Library home page: https://files.pythonhosted.org/packages/5f/bf/93795954016c522008da367da292adceed71cca6ee1717e1d64c83089099/opentelemetry_api-1.40.0-py3-none-any.whl
Sample Path to Dependency File: /examples/trace-analytics-sample-app/sample-app/requirements.txt
Path to vulnerable library: /tmp/ws-ua_20261120230458_JTRJRK/python_QLMXBQ/202611202304591/site-packages-1/opentelemetry_api-1.40.0.dist-info
Dependency Hierarchy:
- opentelemetry_exporter_otlp-1.40.0-py3-none-any.whl (Root Library)
- opentelemetry_exporter_otlp_proto_grpc-1.40.0-py3-none-any.whl
- ❌ opentelemetry_api-1.40.0-py3-none-any.whl (Vulnerable Library)
- opentelemetry_exporter_otlp_proto_grpc-1.40.0-py3-none-any.whl
Found in HEAD commit: aff23afca7be6eb37ce42d1448e445bc8b72b853
Found in base branch: main
Vulnerability Details
OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.1, the opentelemetry-api function TraceState.from_header in opentelemetry/trace/span.py, reached through TraceContextTextMapPropagator.extract, parses inbound W3C tracestate headers with an unbounded optional-whitespace regular expression. A malformed header containing a long run of spaces or tabs without a following comma causes quadratic backtracking before the member-count limit is applied. Services using the default W3C Trace Context propagator can therefore spend excessive CPU time on one unauthenticated request when the HTTP server, parser, gateway, or custom carrier accepts a sufficiently large header. The processing can occupy a synchronous worker or delay unrelated requests on the same asynchronous event loop. The impact is limited to availability and does not expose or modify telemetry data or allow code execution. This issue is fixed in version 1.45.1.
Publish Date: 2026-10-22
URL: CVE-2026-114603
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Release Date: 2026-10-22
Fix Resolution (opentelemetry-api): 1.45.1
Direct dependency fix Resolution (opentelemetry-exporter-otlp): 1.45.0
⛑️ Automatic Remediation will be attempted for this issue.
:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.
- Dominant language
- Java
- Stars
- 381
- Forks
- 374
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 50
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opensearch-project/data-prepper
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
opensearch-project/data-prepper#7313 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability untriaged
Difficulty 1/5 Under an hour Newbie friendliness 65/100
opensearch-project/data-prepper#7305 ·
Maintainers usually reply within 1 day
-
[BUG] Parquet codec wraps list elements in records for files without Avro schema metadataPossibly taken @rohan4naik claimed this today. Openbug untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opensearch-project/data-prepper#7292 ·
Maintainers usually reply within 1 day
-
untriaged
Difficulty 1/5 Under an hour Newbie friendliness 82/100
opensearch-project/data-prepper#7229 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
opensearch-project/data-prepper#7219 ·
Maintainers usually reply within 1 day
All issues in opensearch-project/data-prepper
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
checkstyle/checkstyle#22914 · 1 comment ·
Maintainers usually reply within 1 day
-
component/data-layer
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
RegistryExceptionHandler uses self-referencing basePackageClasses instead of a controller classOpenbug finsim-registry good-first-issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
CVSS