Skip to content

OCPBUGS-101695: bump golang.org/x/net to v0.56.0 - #10749

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sunku5494:CVE-2026-42502-main
Aug 9, 2026
Merged

OCPBUGS-101695: bump golang.org/x/net to v0.56.0#10749
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sunku5494:CVE-2026-42502-main

Conversation

@sunku5494

@sunku5494 sunku5494 commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Updates golang.org/x/net package to v0.56.0 to pull in recent security patches, specifically targeting CVE-2026-42502. While our codebase does not currently use any of the vulnerable symbols identified in the CVE, this update keeps main aligned with the latest secure package version as a proactive measure.

Summary by CodeRabbit

  • Chores
    • Updated an underlying networking dependency to the latest supported version.

@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-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 7, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This pull request references Jira Issue OCPBUGS-101664, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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

Details

In response to this:

Updates golang.org/x/net package to v0.56.0 to pull in recent security patches, specifically targeting CVE-2026-42502. While our codebase does not currently use any of the vulnerable symbols identified in the CVE, this update keeps main aligned with the latest secure package version as a proactive measure.

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.

@openshift-ci
openshift-ci Bot requested review from rochacbruno and tthvo August 7, 2026 17:10
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

The pull request updates the indirect golang.org/x/net dependency from v0.55.0 to v0.56.0 in go.mod.

Changes

Dependency update

Layer / File(s) Summary
Update golang.org/x/net version
go.mod
The indirect dependency changes from v0.55.0 to v0.56.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The commit changes dependency manifests and vendored x/net code only; it adds no test files or Ginkgo test titles.
Test Structure And Quality ✅ Passed The commit changes dependency metadata and vendored x/net sources only; it adds or modifies no Ginkgo tests, so the test-structure criteria are not applicable.
Microshift Test Compatibility ✅ Passed No new Ginkgo or e2e tests were added; the commit updates go.mod, go.sum, vendor metadata, and vendored x/net code only.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR adds no Ginkgo e2e tests or test-like paths; it only updates golang.org/x/net metadata and vendored code, so SNO compatibility checks do not apply.
Topology-Aware Scheduling Compatibility ✅ Passed The commit changes only dependency metadata and vendored golang.org/x/net files; it adds no deployment manifests, operator/controller code, or scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The pull request changes only dependency metadata and vendored x/net code; it adds no OTE binary or process-level stdout setup code.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR changes dependency and vendor files only; it adds no Ginkgo e2e tests, IPv4 assumptions, or external connectivity requirements.
No-Weak-Crypto ✅ Passed The commit only bumps x/net and vendors HTML/HTTP2 changes; no MD5, SHA-1, DES, RC4, Blowfish, ECB, custom crypto, or secret comparisons were added.
Container-Privileges ✅ Passed The diff changes only Go dependency metadata and vendored Go files; no container or Kubernetes manifest changed, and no privilege-setting addition appears.
No-Sensitive-Data-In-Logs ✅ Passed The commit updates go.mod/go.sum and vendored x/net code; added-line and AST scans found no logging calls or sensitive-data output.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the dependency update and specifies the new version, which matches the pull request changes.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This pull request references Jira Issue OCPBUGS-101664, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

Updates golang.org/x/net package to v0.56.0 to pull in recent security patches, specifically targeting CVE-2026-42502. While our codebase does not currently use any of the vulnerable symbols identified in the CVE, this update keeps main aligned with the latest secure package version as a proactive measure.

Summary by CodeRabbit

  • Chores
  • Updated an underlying networking dependency to the latest supported version.

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 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
go.mod (2)

333-333: 🔒 Security & Privacy | 🔵 Trivial

Confirm the release supply-chain controls.

The exact dependency version and checksum metadata are present. The supplied change does not show SBOM generation, provenance attestations, or Sigstore/cosign signing for released artifacts. Confirm these controls in the release workflow before merging.

As per path instructions, production dependency updates require SBOM/provenance attestations and signed artifacts.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@go.mod` at line 333, Confirm the release workflow includes SBOM generation,
provenance attestations, and Sigstore/cosign signing for released artifacts
associated with the golang.org/x/net dependency update. Add any missing controls
before merging while preserving the pinned version and checksum metadata.

Source: Path instructions


333-333: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Update golang.org/x/net to v0.57.0.

v0.57.0 requires Go 1.25.0, and this repository uses Go 1.26.0. Run the documented go get, go mod tidy, and go mod vendor workflow, then commit vendored changes separately.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@go.mod` at line 333, Update the golang.org/x/net dependency from v0.56.0 to
v0.57.0 in the module dependency configuration, then run the documented go get,
go mod tidy, and go mod vendor workflow using the repository’s Go 1.26.0
toolchain. Commit the resulting vendored changes separately.

Source: MCP tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@go.mod`:
- Line 333: Confirm the release workflow includes SBOM generation, provenance
attestations, and Sigstore/cosign signing for released artifacts associated with
the golang.org/x/net dependency update. Add any missing controls before merging
while preserving the pinned version and checksum metadata.
- Line 333: Update the golang.org/x/net dependency from v0.56.0 to v0.57.0 in
the module dependency configuration, then run the documented go get, go mod
tidy, and go mod vendor workflow using the repository’s Go 1.26.0 toolchain.
Commit the resulting vendored changes separately.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 24207640-eb09-4eb6-bb26-21c15553b421

📥 Commits

Reviewing files that changed from the base of the PR and between 2ac6b6e and fc411b1.

⛔ Files ignored due to path filters (9)
  • go.sum is excluded by !**/*.sum
  • vendor/golang.org/x/net/html/entity.go is excluded by !vendor/**, !**/vendor/**
  • vendor/golang.org/x/net/html/escape.go is excluded by !vendor/**, !**/vendor/**
  • vendor/golang.org/x/net/html/foreign.go is excluded by !vendor/**, !**/vendor/**
  • vendor/golang.org/x/net/html/parse.go is excluded by !vendor/**, !**/vendor/**
  • vendor/golang.org/x/net/html/token.go is excluded by !vendor/**, !**/vendor/**
  • vendor/golang.org/x/net/http2/server_wrap.go is excluded by !vendor/**, !**/vendor/**
  • vendor/golang.org/x/net/http2/transport_wrap.go is excluded by !vendor/**, !**/vendor/**
  • vendor/modules.txt is excluded by !vendor/**, !**/vendor/**
📒 Files selected for processing (1)
  • go.mod

Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@sunku5494
sunku5494 force-pushed the CVE-2026-42502-main branch from fc411b1 to 72c0a9b Compare August 7, 2026 17:21
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@sunku5494 sunku5494 changed the title OCPBUGS-101664: bump golang.org/x/net to v0.56.0 OCPBUGS-101695: bump golang.org/x/net to v0.56.0 Aug 7, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This pull request references Jira Issue OCPBUGS-101695, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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

Details

In response to this:

Updates golang.org/x/net package to v0.56.0 to pull in recent security patches, specifically targeting CVE-2026-42502. While our codebase does not currently use any of the vulnerable symbols identified in the CVE, this update keeps main aligned with the latest secure package version as a proactive measure.

Summary by CodeRabbit

  • Chores
  • Updated an underlying networking dependency to the latest supported version.

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.

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This pull request references Jira Issue OCPBUGS-101695, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

Updates golang.org/x/net package to v0.56.0 to pull in recent security patches, specifically targeting CVE-2026-42502. While our codebase does not currently use any of the vulnerable symbols identified in the CVE, this update keeps main aligned with the latest secure package version as a proactive measure.

Summary by CodeRabbit

  • Chores
  • Updated an underlying networking dependency to the latest supported version.

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.

@tthvo tthvo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 7, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 7, 2026
@sunku5494

Copy link
Copy Markdown
Contributor Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 9, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@openshift-ci

openshift-ci Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

@sunku5494: all tests passed!

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit c5c2be7 into openshift:main Aug 9, 2026
15 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: Jira Issue Verification Checks: Jira Issue OCPBUGS-101695
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-101695 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Updates golang.org/x/net package to v0.56.0 to pull in recent security patches, specifically targeting CVE-2026-42502. While our codebase does not currently use any of the vulnerable symbols identified in the CVE, this update keeps main aligned with the latest secure package version as a proactive measure.

Summary by CodeRabbit

  • Chores
  • Updated an underlying networking dependency to the latest supported version.

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.

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 5.0.0-0.nightly-2026-08-09-185812

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants