Skip to content

OCPBUGS-77124: [release-4.17] CVE-2026-26996 Bump minimatch library#16345

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.17from
Atharva-Shinde:4.17-CVE-2026-26996
Jul 3, 2026
Merged

OCPBUGS-77124: [release-4.17] CVE-2026-26996 Bump minimatch library#16345
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.17from
Atharva-Shinde:4.17-CVE-2026-26996

Conversation

@Atharva-Shinde

Copy link
Copy Markdown
Contributor

To remediate GHSA-3ppc-4f35-3m26 this PR bumps the minimatch library to the patched versions.

@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. labels Apr 27, 2026
@coderabbitai

coderabbitai Bot commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

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: Enterprise

Run ID: 25340d66-7d02-405d-9210-4dfe45233cbe

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
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 27, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: This pull request references Jira Issue OCPBUGS-77125, which is invalid:

  • expected the vulnerability to target either version "4.17." or "openshift-4.17.", but it targets "4.18.z" instead
  • 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 dependent Jira Issue OCPBUGS-77126 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead
  • expected dependent Jira Issue OCPBUGS-77126 to target a version in 4.18.0, 4.18.z, but it targets "4.19.z" 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:

To remediate GHSA-3ppc-4f35-3m26 this PR bumps the minimatch library to the patched versions.

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 cajieh and rawagner April 27, 2026 06:24
@jhadvig

jhadvig commented Apr 29, 2026

Copy link
Copy Markdown
Member

/retest

@Atharva-Shinde Atharva-Shinde changed the title OCPBUGS-77125: [release-4.17] CVE-2026-26996 Bump minimatch library OCPBUGS-77124: [release-4.17] CVE-2026-26996 Bump minimatch library May 5, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: This pull request references Jira Issue OCPBUGS-77124, 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 dependent Jira Issue OCPBUGS-77125 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED 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:

To remediate GHSA-3ppc-4f35-3m26 this PR bumps the minimatch library to the patched versions.

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.

@jhadvig

jhadvig commented May 15, 2026

Copy link
Copy Markdown
Member

/retest

@Atharva-Shinde

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console

3 similar comments
@Atharva-Shinde

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console

@Atharva-Shinde

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console

@sg00dwin

Copy link
Copy Markdown
Member

/test e2e-gcp-console

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 22, 2026
Signed-off-by: Atharva Shinde <atshinde@redhat.com>
@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 25, 2026
@miyadav

miyadav commented Jun 25, 2026

Copy link
Copy Markdown
Member

/test e2e-gcp-console

1 similar comment
@miyadav

miyadav commented Jun 26, 2026

Copy link
Copy Markdown
Member

/test e2e-gcp-console

@TheRealJon

Copy link
Copy Markdown
Member

/retest

@TheRealJon TheRealJon 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.

/backport-risk-assessed
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2026
@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Atharva-Shinde, TheRealJon

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 Jul 2, 2026
@TheRealJon

Copy link
Copy Markdown
Member

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 2, 2026
@TheRealJon

Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 2, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-77125 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-77125 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

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:

/jira refresh

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.

@TheRealJon

TheRealJon commented Jul 2, 2026

Copy link
Copy Markdown
Member

/verrified by CI
/override ci/prow/e2e-gcp-console

CI has been broken in 4.18 and earlier for a while. We're investigating: https://redhat.atlassian.net/browse/OCPBUGS-94174

@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

@TheRealJon: Overrode contexts on behalf of TheRealJon: ci/prow/e2e-gcp-console

Details

In response to this:

/verrified by CI
/override ci/prow/e2e-gcp-console

CI has been broken in 4.18 and earlier for a while. We're investigating.

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.

@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: 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.

@Atharva-Shinde

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 Jul 3, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: 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-merge-bot openshift-merge-bot Bot merged commit 2d69b55 into openshift:release-4.17 Jul 3, 2026
7 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@Atharva-Shinde: Jira Issue Verification Checks: Jira Issue OCPBUGS-77124
✔️ 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-77124 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:

To remediate GHSA-3ppc-4f35-3m26 this PR bumps the minimatch library to the patched versions.

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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.

7 participants