Fix for OCPBUGS-81600: CVE-2026-4800

[germanparente]

CVE-2026-4800: Arbitrary code execution via untrusted input in template imports

[openshift-ci-robot]

@germanparente: This pull request references Jira Issue OCPBUGS-81600, which is invalid:

• expected dependent Jira Issue OCPBUGS-81604 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:

CVE-2026-4800: Arbitrary code execution via untrusted input in template imports

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]

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: c17d99b6-d950-4e14-8160-ba3ab0f1ed20

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

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[germanparente]

/test e2e-gcp-console

[germanparente]

/test e2e-gcp-console

[germanparente]

/jira refresh

[openshift-ci-robot]

@germanparente: This pull request references Jira Issue OCPBUGS-81600, 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-81604 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-81604 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.

[germanparente]

/test e2e-gcp-console

[germanparente]

/test e2e-gcp-console

[germanparente]

/test e2e-gcp-console

[germanparente]

/label backport-risk-assessed

[germanparente]

/label backport-risk-assessed

[germanparente]

The e2e-gcp-console failure is not related to this PR's changes. The Cypress e2e tests timed out after ~4 hours, with infrastructure lease renewal failures (502/503 errors) during the run. All tests that completed before the timeout passed successfully.

/retest

[germanparente]

more than 5 runs and assessment that the PR is not related with the failure:

/override ci/prow/e2e-gcp-console

[openshift-ci]

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

Details

In response to this:

more than 5 runs and assessment that the PR is not related with the failure:

/override ci/prow/e2e-gcp-console

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.

[prabhapa]

/lgtm
/label approved
/verified by CI

[openshift-ci-robot]

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

Details

In response to this:

/lgtm
/label approved
/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]

Scheduling required tests:
/test e2e-gcp-console

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• frontend/OWNERS

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

[germanparente]

The approve label was already done here.

/label approved

[germanparente]

the test was already overriden

/override ci/prow/e2e-gcp-console

[openshift-ci]

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

Details

In response to this:

the test was already overriden

/override ci/prow/e2e-gcp-console

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.

[germanparente]

/retest

[germanparente]

/test backend

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD b392b2b and 2 for PR HEAD e20891d in total

[germanparente]

/test backend

[germanparente]

CI Failure Analysis: pull-ci-openshift-console-release-4.17-backend

Verdict: Flake — unrelated to this PR.

The failure is in pkg/helm/actions backend Go tests, while this PR only changes frontend files (frontend/package.json, frontend/packages/console-plugin-shared/package.json, frontend/yarn.lock).

Root Cause

TestMain in setup_test.go:24 panics because cacertCreate.sh fails with exit status 1. The underlying error is a connection refused (errno=111) during an OpenSSL connect call — the local ChartMuseum TLS server wasn't ready before the cert verification script ran.

connect:errno=111
panic: Error waiting program :./testdata/cacertCreate.sh::exit status 1

This is a race condition in the helm test setup and has been observed across multiple retests. All other test packages pass.

/retest

[openshift-ci]

@germanparente: 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-console	e20891d	link	true	/test e2e-gcp-console

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-ci-robot]

@germanparente: An error was encountered invalid pull identifier with 2 parts: "advisories/GHSA-35jh-r3h4-6jhm" for bug OCPBUGS-81600 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message.

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.Jira Issue Verification Checks: Jira Issue OCPBUGS-81600
✔️ 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-81600 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:

CVE-2026-4800: Arbitrary code execution via untrusted input in template imports

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.