Skip to content

OCPBUGS-96585 OCPBUGS-96584: CVE-2026-27136 openshift4/ingress-node-firewall-rhel9-operator: golang.org/x/net/html - #760

Open
dasanind wants to merge 1 commit into
openshift:release-4.22from
dasanind:fix-OCPBUGS-96585-96584
Open

OCPBUGS-96585 OCPBUGS-96584: CVE-2026-27136 openshift4/ingress-node-firewall-rhel9-operator: golang.org/x/net/html#760
dasanind wants to merge 1 commit into
openshift:release-4.22from
dasanind:fix-OCPBUGS-96585-96584

Conversation

@dasanind

Copy link
Copy Markdown

FIXES: OCPBUGS-96585, OCPBUGS-96584

  • Bump golang.org/x/net from v0.37.0 to v0.55.0
  • Required transitive bumps
    • golang.org/x/crypto from v0.36.0 to v0.51.0 ==> Required by x/net v0.55.0
    • golang.org/x/sys from v0.32.0 to v0.45.0 ==> Required by x/net v0.55.0
    • golang.org/x/term from v0.30.0 to v0.43.0 ==> Required by x/net v0.55.0
    • golang.org/x/text from v0.23.0 to v0.37.0 ==> Required by x/net v0.55.0
    • golang.org/x/sync from v0.12.0 to v0.20.0 ==> Required by x/net v0.55.0

Signed-off-by: anidas@redhat.com

  Bump golang.org/x/net from v0.37.0 to v0.55.0 to address CVE-2026-27136

  Transitive dependency bumps required by x/net v0.55.0:
  - golang.org/x/crypto v0.36.0 → v0.51.0
  - golang.org/x/sync v0.12.0 → v0.20.0
  - golang.org/x/sys v0.32.0 → v0.45.0
  - golang.org/x/term v0.30.0 → v0.43.0
  - golang.org/x/text v0.23.0 → v0.37.0

Signed-off-by: Anindita Das <anidas@redhat.com>
@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 Jul 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@dasanind: This pull request references Jira Issue OCPBUGS-96585, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-96585 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

This pull request references Jira Issue OCPBUGS-96584, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-96584 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

FIXES: OCPBUGS-96585, OCPBUGS-96584

  • Bump golang.org/x/net from v0.37.0 to v0.55.0
  • Required transitive bumps
    • golang.org/x/crypto from v0.36.0 to v0.51.0 ==> Required by x/net v0.55.0
    • golang.org/x/sys from v0.32.0 to v0.45.0 ==> Required by x/net v0.55.0
    • golang.org/x/term from v0.30.0 to v0.43.0 ==> Required by x/net v0.55.0
    • golang.org/x/text from v0.23.0 to v0.37.0 ==> Required by x/net v0.55.0
    • golang.org/x/sync from v0.12.0 to v0.20.0 ==> Required by x/net v0.55.0

Signed-off-by: anidas@redhat.com

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 Jul 30, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ce1c2cad-424b-44bc-8cde-de1ae98bc6d8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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 abhat and jcaamano July 30, 2026 04:53
@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dasanind
Once this PR has been reviewed and has the lgtm label, please assign danwinship 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

@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

@dasanind: 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.

@MrSanketkumar

Copy link
Copy Markdown

Hi @dasanind, thanks for raising this PR. I wanted to clarify the intent here I've done a full analysis (govulncheck + 4-algorithm call graph + vendor inspection + manual review) and confirmed that the golang.org/x/net/html vulnerable functions (Parse, ParseFragment, Render) are never called in our codebase. The dependency chain is test-only (k8sreporter → sanitize.BaseName() which is pure string manipulation, no HTML parsing). So from a CVE-2026-27136 perspective, we're not vulnerable and the trackers could be closed as "Not a Bug." was this PR raised for compliance purposes rather than exploitability? If it's compliance-driven, we'd need to apply the same bump across all tracked versions (4.22 through 4.12), not just this one. Would appreciate your clarification so we can align on the right approach.

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.

3 participants