Skip to content

Fix for OCPBUGS-89702: CVE-2026-12143#1090

Open
rhdmalone wants to merge 1 commit into
openshift:release-4.21from
rhdmalone:release-4.21-CVE-2026-12143
Open

Fix for OCPBUGS-89702: CVE-2026-12143#1090
rhdmalone wants to merge 1 commit into
openshift:release-4.21from
rhdmalone:release-4.21-CVE-2026-12143

Conversation

@rhdmalone

Copy link
Copy Markdown
Contributor

Jira: https://redhat.atlassian.net/browse/OCPBUGS-89702
CVE: https://www.cve.org/CVERecord?id=CVE-2026-12143

Fix for GHSA-hmw2-7cc7-3qxx: form-data does not escape CR/LF/quote in multipart field names and filenames (CRLF injection)
updates form-data to 4.0.6 or higher and makes other associated changes

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

Copy link
Copy Markdown

@rhdmalone: This pull request references Jira Issue OCPBUGS-89702, which is invalid:

  • expected Jira Issue OCPBUGS-89702 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Jira: https://redhat.atlassian.net/browse/OCPBUGS-89702
CVE: https://www.cve.org/CVERecord?id=CVE-2026-12143

Fix for GHSA-hmw2-7cc7-3qxx: form-data does not escape CR/LF/quote in multipart field names and filenames (CRLF injection)
updates form-data to 4.0.6 or higher and makes other associated changes

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 23, 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: c42a2936-2db8-45b5-98b9-d43040c2837a

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
openshift-ci Bot requested review from etmurasaki and jgbernalp July 23, 2026 15:50
@rhdmalone

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@rhdmalone: This pull request references Jira Issue OCPBUGS-89702, which is invalid:

  • expected dependent Jira Issue OCPBUGS-89698 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
  • expected dependent Jira Issue OCPBUGS-89698 to target a version in 4.22.0, but it targets "4.22.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.

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.

@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

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

@jgbernalp

Copy link
Copy Markdown
Contributor

/lgtm

@jgbernalp

Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jul 23, 2026
@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 23, 2026
@jgbernalp

Copy link
Copy Markdown
Contributor

/lgtm

@jgbernalp

Copy link
Copy Markdown
Contributor

/test ?

@jgbernalp

Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

@jgbernalp: The following commands are available to trigger required jobs:

/test images
/test lint
/test okd-scos-images
/test periodics-images
/test translations
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-alerts
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test e2e-coo
/test e2e-dashboards
/test e2e-hypershift-conformance
/test e2e-incidents
/test e2e-metrics
/test e2e-monitoring
/test e2e-monitoring-bvt
/test e2e-monitoring-dev
/test e2e-monitoring-reg
/test e2e-virtualization
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-monitoring-plugin-release-4.21-images
pull-ci-openshift-monitoring-plugin-release-4.21-lint
pull-ci-openshift-monitoring-plugin-release-4.21-okd-scos-images
pull-ci-openshift-monitoring-plugin-release-4.21-periodics-images
pull-ci-openshift-monitoring-plugin-release-4.21-translations
pull-ci-openshift-monitoring-plugin-release-4.21-verify-deps
Details

In response to this:

/test ?

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 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, rhdmalone

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

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/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. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants