Skip to content

OCPBUGS-101788: Bump postcss to fix CVE-2026-69153 - #17113

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

OCPBUGS-101788: Bump postcss to fix CVE-2026-69153#17113
prabhapa wants to merge 1 commit into
openshift:release-4.15from
prabhapa:cve/release-4.15/OCPBUGS-101788

Conversation

@prabhapa

Copy link
Copy Markdown

CVE-2026-69153: PostCSS Information Disclosure

Bumps postcss from 8.4.31 to 8.5.26 (fixed in >=8.5.19) to address CVE-2026-69153.

Vulnerability

PostCSS prior to 8.5.19 allows an attacker to cause PreviousMap.loadFile() to read an unintended source-map file by supplying an absolute or directory-traversal sourceMappingURL when from is unset. The resulting map's sources and sourcesContent may then be exposed to the application.

Changes

  • frontend/package.json: Updated resolutions.postcss from ^8.2.13 to ^8.5.19
  • frontend/yarn.lock: Regenerated — postcss 8.4.31 → 8.5.26 (plus transitive deps nanoid, source-map-js)

Jira

postcss is a transitive dependency (pulled in via css-loader and
sanitize-html) and is pinned through the Yarn `resolutions` field in
frontend/package.json. Updated that resolution from ^8.2.13 to ^8.5.19
to remediate CVE-2026-69153 (information disclosure via a crafted
sourceMappingURL), which is fixed in postcss 8.5.19.

Resolved version in frontend/yarn.lock: 8.4.31 -> 8.5.26.

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

Copy link
Copy Markdown
Contributor

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

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

CVE-2026-69153: PostCSS Information Disclosure

Bumps postcss from 8.4.31 to 8.5.26 (fixed in >=8.5.19) to address CVE-2026-69153.

Vulnerability

PostCSS prior to 8.5.19 allows an attacker to cause PreviousMap.loadFile() to read an unintended source-map file by supplying an absolute or directory-traversal sourceMappingURL when from is unset. The resulting map's sources and sourcesContent may then be exposed to the application.

Changes

  • frontend/package.json: Updated resolutions.postcss from ^8.2.13 to ^8.5.19
  • frontend/yarn.lock: Regenerated — postcss 8.4.31 → 8.5.26 (plus transitive deps nanoid, source-map-js)

Jira

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 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: ee394383-5be9-4cee-b238-ead5c402587b

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
openshift-ci Bot requested review from rhamilto and sg00dwin August 31, 2026 07:22
@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@openshift-ci

openshift-ci Bot commented Aug 31, 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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants