Skip to content

OCPBUGS-100512: Bump postcss to fix CVE-2026-45623 - #17034

Open
redhat-chai-bot wants to merge 1 commit into
openshift:release-4.15from
redhat-chai-bot:CVE-2026-45623-4.15
Open

OCPBUGS-100512: Bump postcss to fix CVE-2026-45623#17034
redhat-chai-bot wants to merge 1 commit into
openshift:release-4.15from
redhat-chai-bot:CVE-2026-45623-4.15

Conversation

@redhat-chai-bot

Copy link
Copy Markdown

Summary

Bump the postcss yarn resolution from ^8.2.13 to ^8.5.12 to address CVE-2026-45623.

CVE Details

  • CVE: CVE-2026-45623
  • Severity: Moderate (CVSS 7.5)
  • CWE: CWE-22 (Path Traversal)
  • Description: PostCSS PreviousMap parses sourceMappingURL comments from CSS input and dereferences the path against the local filesystem with no scheme, allowlist, or traversal check. An attacker who controls CSS input can cause the host process to read arbitrary files.
  • Fixed in: PostCSS 8.5.12+

Changes

  • frontend/package.json: Updated resolutions.postcss from ^8.2.13 to ^8.5.12
  • frontend/yarn.lock: Regenerated (postcss now resolves to 8.5.26)

AI-generated. Review for accuracy.

@prabhapa requested in Slack thread

Update the postcss resolution from ^8.2.13 to ^8.5.12 to address
CVE-2026-45623 (PostCSS: Information disclosure and denial of service
via crafted CSS input).

https://redhat.atlassian.net/browse/OCPBUGS-100512
@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. labels Aug 19, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-100512, which is invalid:

  • expected Jira Issue OCPBUGS-100512 to depend on a bug targeting a version in 4.16.0, 4.16.z 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:

Summary

Bump the postcss yarn resolution from ^8.2.13 to ^8.5.12 to address CVE-2026-45623.

CVE Details

  • CVE: CVE-2026-45623
  • Severity: Moderate (CVSS 7.5)
  • CWE: CWE-22 (Path Traversal)
  • Description: PostCSS PreviousMap parses sourceMappingURL comments from CSS input and dereferences the path against the local filesystem with no scheme, allowlist, or traversal check. An attacker who controls CSS input can cause the host process to read arbitrary files.
  • Fixed in: PostCSS 8.5.12+

Changes

  • frontend/package.json: Updated resolutions.postcss from ^8.2.13 to ^8.5.12
  • frontend/yarn.lock: Regenerated (postcss now resolves to 8.5.26)

AI-generated. Review for accuracy.

@prabhapa requested in Slack thread

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

coderabbitai Bot commented Aug 19, 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: Pro Plus

Run ID: e0323be5-cefb-4bca-b512-3f513fcd3b71

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 cajieh and rhamilto August 19, 2026 06:24
@prabhapa

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@prabhapa: This pull request references Jira Issue OCPBUGS-100512, which is invalid:

  • expected Jira Issue OCPBUGS-100512 to depend on a bug targeting a version in 4.16.0, 4.16.z 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 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

Copy link
Copy Markdown
Contributor

/lgtm

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

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@redhat-chai-bot

Copy link
Copy Markdown
Author

/retest e2e-gcp-console


AI-generated. Review for accuracy.

@redhat-chai-bot

Copy link
Copy Markdown
Author

/test e2e-gcp-console


AI-generated. Review for accuracy.

1 similar comment
@redhat-chai-bot

Copy link
Copy Markdown
Author

/test e2e-gcp-console


AI-generated. Review for accuracy.

@openshift-ci

openshift-ci Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: 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.

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-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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants