Skip to content

[release-5.0] OCPBUGS-107939: CVE-2026-41178 - bump go.opentelemetry.io/otel to v1.44.0 - #263

Open
rissh wants to merge 1 commit into
openshift:release-5.0from
rissh:CVE-2026-41178-release-5.0
Open

[release-5.0] OCPBUGS-107939: CVE-2026-41178 - bump go.opentelemetry.io/otel to v1.44.0#263
rissh wants to merge 1 commit into
openshift:release-5.0from
rissh:CVE-2026-41178-release-5.0

Conversation

@rissh

@rissh rissh commented Aug 21, 2026

Copy link
Copy Markdown

Summary

Signed-off-by: Rishikesh Jagadale <rjagadal@redhat.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 21, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@rissh: This pull request references Jira Issue OCPBUGS-107939, which is invalid:

  • expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "5.0.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Backport of OCPBUGS-112564: Fix CVE-2026-41178 - bump go.opentelemetry.io/otel to v1.44.0 #262 (main / 5.1) onto release-5.0.
  • Bumps indirect go.opentelemetry.io/otel (and matching otel/metric, otel/trace) from v1.43.0 to v1.44.0 and vendors the result.
  • Addresses CVE-2026-41178 (GO-2026-5158): unbounded baggage Parse on otel v1.41.0 and v1.43.0. The code fix is OpenTelemetry-Go #8222 in v1.44.0.
  • Same change as PR 262: no first-party logic updates, dependency pin only.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 3192213d-b27f-44e3-a7cb-7933941d22ce


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from marty-power and miheer August 21, 2026 20:01
@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rissh
Once this PR has been reviewed and has the lgtm label, please assign jcaamano for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rissh
rissh changed the base branch from main to release-5.0 August 21, 2026 20:04
@openshift-ci-robot

Copy link
Copy Markdown

@rissh: This pull request references Jira Issue OCPBUGS-107939, which is invalid:

  • expected dependent Jira Issue OCPBUGS-112564 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Summary

  • Backport of OCPBUGS-112564: Fix CVE-2026-41178 - bump go.opentelemetry.io/otel to v1.44.0 #262 (main / 5.1) onto release-5.0.
  • Bumps indirect go.opentelemetry.io/otel (and matching otel/metric, otel/trace) from v1.43.0 to v1.44.0 and vendors the result.
  • Addresses CVE-2026-41178 (GO-2026-5158): unbounded baggage Parse on otel v1.41.0 and v1.43.0. The code fix is OpenTelemetry-Go #8222 in v1.44.0.
  • Same change as PR 262: no first-party logic updates, dependency pin only.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@rissh

rissh commented Aug 21, 2026

Copy link
Copy Markdown
Author

/pipeline required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-ovn
/test e2e-azure-ovn
/test e2e-azure-serial-1of2
/test e2e-azure-serial-2of2
/test e2e-gcp-ovn
/test hypershift-e2e-aks

@rissh

rissh commented Aug 22, 2026

Copy link
Copy Markdown
Author

/retest

@openshift-ci

openshift-ci Bot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

@rissh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-ovn 1002b5a link true /test e2e-gcp-ovn

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants