Skip to content

OCPBUGS-100511: Bump postcss to fix CVE-2026-45623 - #17109

Open
prabhapa wants to merge 1 commit into
openshift:release-4.14from
prabhapa:cve/release-4.14/OCPBUGS-100511
Open

OCPBUGS-100511: Bump postcss to fix CVE-2026-45623#17109
prabhapa wants to merge 1 commit into
openshift:release-4.14from
prabhapa:cve/release-4.14/OCPBUGS-100511

Conversation

@prabhapa

Copy link
Copy Markdown

CVE-2026-45623: PostCSS Information Disclosure and DoS

Bumps postcss to remediate CVE-2026-45623 (CVSS 7.5 Moderate).

PostCSS versions ≤8.5.11 parse sourceMappingURL comments and dereference paths against the local filesystem without validation, enabling file-read disclosure and DoS. Fixed in postcss ≥8.5.12.

Changes

  • postcss: 8.4.31 → 8.5.26 (via resolutions in frontend/package.json)
  • Resolution range updated from ^8.2.13 to ^8.5.12
  • Lockfile (frontend/yarn.lock) regenerated

Sub-dependency updates (automatic via lockfile):

  • nanoid 3.3.6 → 3.3.18
  • picocolors 1.0.0 → 1.1.1
  • source-map-js 1.0.2 → 1.2.1

Validation

  • Clean yarn install
  • postcss functional verification (processes CSS correctly at 8.5.26)
  • All postcss consumers resolve to 8.5.26
  • Unit tests pass (jest 2/2)
  • Lint clean (eslint)

References

Bump postcss from 8.4.31 to 8.5.26 (>=8.5.12) to remediate
CVE-2026-45623 (PostCSS information disclosure and DoS via crafted
CSS input).

postcss is a transitive dependency (via css-loader and sanitize-html)
pinned through the "resolutions" field in frontend/package.json.
Updated the resolution from ^8.2.13 to ^8.5.12 and regenerated
frontend/yarn.lock.

Related: OCPBUGS-100511

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@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 31, 2026
@coderabbitai

coderabbitai Bot commented Aug 31, 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: 174d0ceb-c9ef-40d6-811a-99485ca1dc34

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

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

Copy link
Copy Markdown
Contributor

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

  • expected dependent Jira Issue OCPBUGS-100512 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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-45623: PostCSS Information Disclosure and DoS

Bumps postcss to remediate CVE-2026-45623 (CVSS 7.5 Moderate).

PostCSS versions ≤8.5.11 parse sourceMappingURL comments and dereference paths against the local filesystem without validation, enabling file-read disclosure and DoS. Fixed in postcss ≥8.5.12.

Changes

  • postcss: 8.4.31 → 8.5.26 (via resolutions in frontend/package.json)
  • Resolution range updated from ^8.2.13 to ^8.5.12
  • Lockfile (frontend/yarn.lock) regenerated

Sub-dependency updates (automatic via lockfile):

  • nanoid 3.3.6 → 3.3.18
  • picocolors 1.0.0 → 1.1.1
  • source-map-js 1.0.2 → 1.2.1

Validation

  • Clean yarn install
  • postcss functional verification (processes CSS correctly at 8.5.26)
  • All postcss consumers resolve to 8.5.26
  • Unit tests pass (jest 2/2)
  • Lint clean (eslint)

References

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 jhadvig and rhamilto August 31, 2026 06:06
@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 Sep 1, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

[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 cajieh 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

@prabhapa

prabhapa commented Sep 1, 2026

Copy link
Copy Markdown
Author

/test e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

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

@prabhapa

prabhapa commented Sep 2, 2026

Copy link
Copy Markdown
Author

/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 Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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