Skip to content

[release-4.22] Address CVE-2026-118664: upgrade decode-uri-component to 0.5.1 - #17455

Open
germanparente wants to merge 1 commit into
openshift:release-4.22from
openshift-sustaining:release-4.22_CVE-2026-118664
Open

germanparente wants to merge 1 commit into
openshift:release-4.22from
openshift-sustaining:release-4.22_CVE-2026-118664

Conversation

@germanparente

Copy link
Copy Markdown
Contributor

Summary

  • Adds a yarn resolution to force decode-uri-component to 0.5.1, fixing CVE-2026-118664
  • CVE-2026-118664 is a quadratic complexity Denial of Service vulnerability (CVSS 7.5) in decode-uri-component < 0.5.1
  • The vulnerable package (v0.2.0) was pulled in transitively via query-string and source-map-resolve

Details

Prior to 0.5.1, decodeUriComponent falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regex replacement for each entry. Malformed input containing many distinct runs causes quadratic CPU consumption, blocking the Node.js event loop.

Test plan

  • yarn install completes successfully
  • decode-uri-component resolves to 0.5.1 in yarn.lock
  • CI passes

🤖 Generated with Claude Code

Add a yarn resolution to force decode-uri-component to 0.5.1,
fixing a quadratic complexity DoS vulnerability (CVSS 7.5).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@germanparente: No Jira issue with key CVE-2026 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Summary

  • Adds a yarn resolution to force decode-uri-component to 0.5.1, fixing CVE-2026-118664
  • CVE-2026-118664 is a quadratic complexity Denial of Service vulnerability (CVSS 7.5) in decode-uri-component < 0.5.1
  • The vulnerable package (v0.2.0) was pulled in transitively via query-string and source-map-resolve

Details

Prior to 0.5.1, decodeUriComponent falls back to customDecodeURIComponent after native decoding throws, and the fallback collects every distinct percent-encoded run before performing a full-string regex replacement for each entry. Malformed input containing many distinct runs causes quadratic CPU consumption, blocking the Node.js event loop.

Test plan

  • yarn install completes successfully
  • decode-uri-component resolves to 0.5.1 in yarn.lock
  • CI passes

🤖 Generated with Claude Code

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

Copy link
Copy Markdown
Contributor

Pipeline controller notification

This PR uses the pipeline controller for second-stage tests. Selection and triggering follow the repository configuration.

Use /test ? to list jobs and /pipeline help for commands.

@openshift-ci

openshift-ci Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

Copy link
Copy Markdown
Contributor

@germanparente: The following tests 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/images 033037f link true /test images
ci/prow/frontend 033037f link true /test frontend

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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants