Skip to content

OCPBUGS-101787: Bump postcss to fix CVE-2026-69153 - #17111

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

OCPBUGS-101787: Bump postcss to fix CVE-2026-69153#17111
prabhapa wants to merge 1 commit into
openshift:release-4.14from
prabhapa:cve/release-4.14/OCPBUGS-101787

Conversation

@prabhapa

Copy link
Copy Markdown

CVE-2026-69153: PostCSS Information Disclosure

Bumps postcss from 8.4.31 to 8.5.19 to fix 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.

  • CVSS v3: 7.5 (Important)
  • CWE: CWE-22 (Path Traversal)
  • Fix: postcss 8.5.19
  • Advisory: GHSA-fxqj-rqcc-2cmp

Changes

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

Validation

  • yarn install --immutable passes (lockfile integrity — same gate CI enforces)
  • Runtime resolution confirms single copy of postcss@8.5.19

Jira

Pin the postcss resolution to 8.5.19 (previously ^8.2.13, resolving to 8.4.31) to remediate CVE-2026-69153, an information-disclosure issue via a crafted sourceMappingURL in PostCSS. postcss is a transitive dependency; the existing resolutions entry in frontend/package.json is updated to force the fixed version and frontend/yarn.lock is regenerated accordingly.

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. 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: c0e3285d-ba8a-4cc5-a5d5-e2d5a44d1a38

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-101787, which is invalid:

  • expected dependent Jira Issue OCPBUGS-101788 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-69153: PostCSS Information Disclosure

Bumps postcss from 8.4.31 to 8.5.19 to fix 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.

  • CVSS v3: 7.5 (Important)
  • CWE: CWE-22 (Path Traversal)
  • Fix: postcss 8.5.19
  • Advisory: GHSA-fxqj-rqcc-2cmp

Changes

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

Validation

  • yarn install --immutable passes (lockfile integrity — same gate CI enforces)
  • Runtime resolution confirms single copy of postcss@8.5.19

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.

@openshift-ci
openshift-ci Bot requested review from TheRealJon and spadgett August 31, 2026 06:20
@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 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

@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

@prabhapa: 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/backend 8c27135 link true /test backend

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