temporalio / temporalio/temporal

Security: CVE-2026-41178 — go.opentelemetry.io/otel/propagation v1.43.0 DoS via unbounded baggage header parsing

Open
#10,885 0 comments 0 reactions 1 assignee View on GitHub

@yycptt is already working on this.

Since Jul 9, 2026.

Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Description

Running a Twistlock / Prisma Cloud scan against temporalio/server:1.31.1 and temporalio/admin-tools:1.31.1 surfaces CVE-2026-41178 in the bundled go.opentelemetry.io/otel/propagation dependency.

Vulnerability details
Field Detail
CVE CVE-2026-41178
Advisory https://advisories.gitlab.com/golang/go.opentelemetry.io/otel/propagation/CVE-2026-41178/
Package go.opentelemetry.io/otel/propagation
Bundled version v1.43.0 (confirmed via go.sum in temporal v1.31.1)
Fixed versions v1.42.0 or v1.44.0+
Severity MEDIUM — CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)
CWE CWE-789 (Memory Allocation with Excessive Size Value)
Published May 28, 2026
Root cause

A change in open-telemetry/opentelemetry-go#7880 removed the raw-length cap on baggage header parsing. As a result, Parse() will process arbitrarily large or malformed baggage HTTP headers, causing excessive CPU/memory consumption and log amplification. Any Temporal service using the default OTel baggage propagator and accepting external HTTP traffic is exposed to availability impact.

Affected versions
  • go.opentelemetry.io/otel v1.41.0 – v1.41.x (before 1.42.0)
  • go.opentelemetry.io/otel v1.43.0 – v1.43.x (before 1.44.0) ← this repo
Confirmed affected images
  • temporalio/server:1.31.1
  • temporalio/admin-tools:1.31.1
Suggested fix

Bump go.opentelemetry.io/otel (and sub-modules) to v1.44.0 or later in go.mod / go.sum.

go get go.opentelemetry.io/otel@v1.44.0
go get go.opentelemetry.io/otel/propagation@v1.44.0
go mod tidy

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.