Skip to content

chore(deps): update dependency opentelemetry-api to v1.45.2 [security] - abandoned - #124

Open
renovate[bot] wants to merge 2 commits into
masterfrom
renovate/pypi-opentelemetry-api-vulnerability
Open

renovate[bot] wants to merge 2 commits into
masterfrom
renovate/pypi-opentelemetry-api-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
opentelemetry-api 1.45.1 → 1.45.2 age confidence

OpenTelemetry Python API: Denial of service through quadratic-time traceparent parsing

CVE-2026-126360 / GHSA-mf5v-w3w3-f6cg

More information

Details

Summary

TraceContextTextMapPropagator.extract() in opentelemetry-api is vulnerable to regular expression denial of service (ReDoS) when processing a specially crafted traceparent value.

A malformed value containing a trace-context prefix followed by a long whitespace sequence and an embedded newline triggers quadratic-time regex backtracking. Applications that extract trace context from untrusted carriers accepting such strings can experience excessive CPU consumption and request-processing delays.

When extraction runs on an asynchronous server’s event-loop thread, a single malicious message can delay unrelated requests handled by that event loop.

Exposure conditions

Exploitation requires attacker-controlled input to reach the affected propagator through a carrier that preserves embedded newlines and permits a sufficiently large value.

Conforming HTTP header values cannot contain embedded newlines. However, OpenTelemetry carriers are not restricted to HTTP headers. JSON strings can contain escaped newlines that become newline characters after decoding.

MCP request metadata is one relevant integration path: applications may extract trace context from JSON params._meta. Exposure depends on the MCP SDK or instrumentation version, whether extraction invokes the W3C Trace Context propagator, and applicable message-size limits. HTTP header validation does not constrain a traceparent string carried inside a JSON body.

Authentication requirements depend on the application exposing the carrier.

Impact

The demonstrated impact is denial of service through excessive CPU consumption and blocked request processing. Repeated malicious messages may sustain service degradation.

This finding does not demonstrate data disclosure, data modification, or code execution.

Remediation

Upgrade opentelemetry-api to 1.45.2 or a later release containing the fix.

Version 1.45.2 rejects traceparent values longer than 512 characters before regex matching and removes the overlapping suffix and trailing-whitespace expressions.

Where upgrading is temporarily unavailable, reject oversized values and embedded CR/LF characters before passing untrusted trace-context values to the affected propagator.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

open-telemetry/opentelemetry-python (opentelemetry-api)

v1.45.2

Compare Source

Added
  • opentelemetry-sdk, opentelemetry-configuration,
    opentelemetry-exporter-prometheus: enforce metric cardinality limits
    (default 2000) with the otel.metric.overflow attribute, configurable
    through View(aggregation_cardinality_limit=...), reader
    cardinality_limits and declarative configuration
    (#​5809)
Fixed
  • opentelemetry-api: limit traceparent header length to 512 characters in
    TraceContextTextMapPropagator during extraction
    (#​5818)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added dependencies Pull requests that update project dependencies. uv Pull requests that update uv and pip (Python) dependencies. labels Nov 14, 2026
Auto-generated by GitHub Actions from uv export
@github-actions

Copy link
Copy Markdown
Contributor

✅ Backend requirements.txt updated

Generated from backend/uv.lock using uv export --no-hashes --frozen > requirements.txt

@renovate

renovate Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate Bot changed the title chore(deps): update dependency opentelemetry-api to v1.45.2 [security] chore(deps): update dependency opentelemetry-api to v1.45.2 [security] - abandoned Nov 18, 2026
@renovate

renovate Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor Author

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update project dependencies. uv Pull requests that update uv and pip (Python) dependencies.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants