Skip to content

OCPBUGS-98314: bump tar to ^7.5.19 for CVE-2026-59873#16745

Open
Cragsmann wants to merge 1 commit into
openshift:mainfrom
Cragsmann:OCPBUGS-98314
Open

OCPBUGS-98314: bump tar to ^7.5.19 for CVE-2026-59873#16745
Cragsmann wants to merge 1 commit into
openshift:mainfrom
Cragsmann:OCPBUGS-98314

Conversation

@Cragsmann

@Cragsmann Cragsmann commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Analysis / Root cause:

CVE-2026-59873: node-tar prior to 7.5.19 does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio, allowing a small crafted gzip bomb to exhaust disk space and CPU.

Our yarn.lock pinned tar@7.5.7 via the node-gyp build dependency. While this is a build-time only dependency (not shipped in the container image), it triggers security scanner findings against the ose-console-rhel9 image.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-98314

Solution description:

Add a yarn resolutions entry for "tar": "^7.5.19" in frontend/package.json to force the patched version. This follows the established pattern used for other CVE bumps (protobufjs, fast-uri, shell-quote, etc.).

Screenshots / screen recording:

N/A — dependency-only change, no UI impact.

Test setup:

No special setup required.

Test cases:

  • yarn install completes without errors
  • yarn why tar shows 7.5.19+
  • Build completes successfully

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

The tar package is only used at build time by node-gyp for compiling native addons (fsevents, nan, websocket). It is never included in the production bundle or container image.

Reviewers and assignees:

Summary by CodeRabbit

  • Chores
    • Updated package installation settings to use a constrained version of the tar package.
    • Preserved the existing dependency resolution for fast-uri.

node-tar <7.5.19 is vulnerable to a Denial of Service via crafted gzip
bomb (CVE-2026-59873). Add a yarn resolution to force the fixed version.

Co-Authored-By: Claude Opus 4.6 <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/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jul 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@Cragsmann: This pull request references Jira Issue OCPBUGS-98314, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

CVE-2026-59873: node-tar prior to 7.5.19 does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio, allowing a small crafted gzip bomb to exhaust disk space and CPU.

Our yarn.lock pinned tar@7.5.7 via the node-gyp build dependency. While this is a build-time only dependency (not shipped in the container image), it triggers security scanner findings against the ose-console-rhel9 image.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-98314

Solution description:

Add a yarn resolutions entry for "tar": "^7.5.19" in frontend/package.json to force the patched version. This follows the established pattern used for other CVE bumps (protobufjs, fast-uri, shell-quote, etc.).

Screenshots / screen recording:

N/A — dependency-only change, no UI impact.

Test setup:

No special setup required.

Test cases:

  • yarn install completes without errors
  • yarn why tar shows 7.5.19+
  • Build completes successfully

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

The tar package is only used at build time by node-gyp for compiling native addons (fsevents, nan, websocket). It is never included in the production bundle or container image.

Reviewers and assignees:

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 Jul 10, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

Changes

Dependency resolution

Layer / File(s) Summary
Add tar resolution
frontend/package.json
The Yarn resolutions block adds an explicit tar constraint of ^7.5.19 alongside the existing fast-uri resolution.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly matches the change: a Jira-linked tar bump to address CVE-2026-59873.
Description check ✅ Passed The description covers root cause, solution, tests, screenshots, and additional info, with only reviewers left blank.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Only frontend/package.json and yarn.lock changed; no Ginkgo test files or titles were added or modified.
Test Structure And Quality ✅ Passed PR only changes frontend dependency resolutions; no Ginkgo test code or test files were modified, so this test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only frontend/package.json and yarn.lock changed; no Ginkgo test files or OpenShift API usage were added, so the MicroShift check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only changes frontend dependency resolutions and yarn.lock; no Ginkgo e2e tests were added or modified.
Topology-Aware Scheduling Compatibility ✅ Passed Only frontend dependency files changed (package.json and yarn.lock); no deployment manifests, operator code, or controllers were modified.
Ote Binary Stdout Contract ✅ Passed Only frontend/package.json and yarn.lock changed; no process-level Go code or stdout writes are involved.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only frontend/package.json and yarn.lock changed; no new Ginkgo/e2e tests or IPv4/external-network code was added.
No-Weak-Crypto ✅ Passed Diff is dependency-only (tar resolution in package.json/yarn.lock); no weak crypto, custom crypto, or secret comparison code was introduced.
Container-Privileges ✅ Passed PR only changes frontend/package.json and frontend/yarn.lock; no privileged/container security fields are present in the touched files.
No-Sensitive-Data-In-Logs ✅ Passed Only dependency resolution files changed; no source code or logging statements were added.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Copy link
Copy Markdown
Contributor

@Cragsmann: This pull request references Jira Issue OCPBUGS-98314, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

Analysis / Root cause:

CVE-2026-59873: node-tar prior to 7.5.19 does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio, allowing a small crafted gzip bomb to exhaust disk space and CPU.

Our yarn.lock pinned tar@7.5.7 via the node-gyp build dependency. While this is a build-time only dependency (not shipped in the container image), it triggers security scanner findings against the ose-console-rhel9 image.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-98314

Solution description:

Add a yarn resolutions entry for "tar": "^7.5.19" in frontend/package.json to force the patched version. This follows the established pattern used for other CVE bumps (protobufjs, fast-uri, shell-quote, etc.).

Screenshots / screen recording:

N/A — dependency-only change, no UI impact.

Test setup:

No special setup required.

Test cases:

  • yarn install completes without errors
  • yarn why tar shows 7.5.19+
  • Build completes successfully

Browser conformance:

  • Chrome
  • Firefox
  • Safari (or Epiphany on Linux)

Additional info:

The tar package is only used at build time by node-gyp for compiling native addons (fsevents, nan, websocket). It is never included in the production bundle or container image.

Reviewers and assignees:

Summary by CodeRabbit

  • Chores
  • Updated package installation settings to use a constrained version of the tar package.
  • Preserved the existing dependency resolution for fast-uri.

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 jhadvig July 10, 2026 12:12
@openshift-ci

openshift-ci Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Cragsmann
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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/package.json`:
- Line 340: Pin the tar dependency in frontend/package.json to the exact version
7.5.19 by removing the caret prefix, matching the exact-version convention used
by fast-uri.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: e7e3b405-aa20-4406-bf7c-427cd70c19f4

📥 Commits

Reviewing files that changed from the base of the PR and between bc58d07 and 775ee1d.

⛔ Files ignored due to path filters (1)
  • frontend/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (1)
  • frontend/package.json

Comment thread frontend/package.json
"protobufjs": "7.5.8",
"fast-uri": "3.1.2"
"fast-uri": "3.1.2",
"tar": "^7.5.19"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

Pin tar to an exact version instead of using a caret range.

The path instructions for package*.json files require pinning exact versions. The caret range ^7.5.19 allows any future 7.x release, which could introduce new vulnerabilities. The existing fast-uri resolution in the same block already uses an exact pin (3.1.2), so this should be consistent.

🔒 Proposed fix to pin exact version
-    "tar": "^7.5.19"
+    "tar": "7.5.19"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"tar": "^7.5.19"
"tar": "7.5.19"
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@frontend/package.json` at line 340, Pin the tar dependency in
frontend/package.json to the exact version 7.5.19 by removing the caret prefix,
matching the exact-version convention used by fast-uri.

Source: Path instructions

@openshift-ci

openshift-ci Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@Cragsmann: 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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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.

2 participants