derrickaw opened a new pull request, #41357:
URL: https://github.com/apache/beam/pull/41357

   Note: this PR was auto-generated by tooling. Before moving it out of draft, 
the author has done a full review of the PR, specifically evaluating it on the 
following criteria:
   
   - The PR remediates a confirmed, live vulnerability on `master` that 
Dependabot is not already addressing
   - The version update is minimal, respects Beam's compatibility bounds, and 
avoids unrelated dependency churn
   - Relevant lockfiles, package constraints, and tests have been verified
   
   If you have concerns with the PR or with the underlying methodology used to 
generate this, please comment below - they will be addressed by the author not 
the tooling :)
   
   ## Summary
   
   Bumps transitive dependency `tar` (`node-tar`) from `7.4.3` to `7.5.23` 
(along with its transitive `minizlib` requirement from `3.0.1` to `3.1.0`) in 
[`sdks/python/apache_beam/runners/interactive/extensions/apache-beam-jupyterlab-sidepanel/yarn.lock`](https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/interactive/extensions/apache-beam-jupyterlab-sidepanel/yarn.lock)
 to remediate **12 open Dependabot security alerts** (1 Critical, 8 High, 3 
Medium) where Dependabot has no open PR.
   
   ## Remediated Security Advisories
   
   | Dependabot Alert | Advisory | Severity | Vulnerable Range | First Patched 
| Summary |
   | :--- | :--- | :--- | :--- | :--- | :--- |
   | `#2680` | `CVE-2026-59873` (`GHSA-23hp-3jrh-7fpw`) | **Critical** | `<= 
7.5.18` | `7.5.19` | Decompression/parse DoS via unlimited input |
   | `#2888` | `CVE-2026-73566` (`GHSA-r292-9mhp-454m`) | **High** | `<= 
7.5.20` | `7.5.21` | Uncontrolled recursion in `mapHas`/`filesFilter` 
stack-overflow DoS |
   | `#2679` | `CVE-2026-59874` (`GHSA-8x88-c5mf-7j5w`) | **High** | `<= 
7.5.17` | `7.5.18` | Negative tar entry size causes infinite loop in archive 
replace |
   | `#1873` | `CVE-2026-31802` (`GHSA-9ppj-qmqm-q256`) | **High** | `<= 
7.5.10` | `7.5.11` | Symlink path traversal via drive-relative `linkpath` |
   | `#1869` | `CVE-2026-29786` (`GHSA-qffp-2rhf-9h96`) | **High** | `<= 7.5.9` 
| `7.5.10` | Hardlink path traversal via drive-relative `linkpath` |
   | `#1820` | `CVE-2026-26960` (`GHSA-83g3-92jg-28cx`) | **High** | `< 7.5.8` 
| `7.5.8` | Arbitrary file read/write via hardlink target escape through 
symlink chain |
   | `#1756` | `CVE-2026-24842` (`GHSA-34x7-hfp2-rc4v`) | **High** | `< 7.5.7` 
| `7.5.7` | Arbitrary file creation/overwrite via hardlink path traversal |
   | `#1706` | `CVE-2026-23950` (`GHSA-r6q2-hw4h-h46w`) | **High** | `<= 7.5.3` 
| `7.5.4` | Race condition in path reservations via Unicode ligature collisions 
on macOS APFS |
   | `#1702` | `CVE-2026-23745` (`GHSA-8qq5-rm4j-mr97`) | **High** | `<= 7.5.2` 
| `7.5.3` | Arbitrary file overwrite and symlink poisoning via insufficient 
path sanitization |
   | `#2681` | `CVE-2026-59871` (`GHSA-w8wr-v893-vjvp`) | **Medium** | `<= 
7.5.17` | `7.5.18` | Process crash via PAX numeric path type confusion |
   | `#2678` | `CVE-2026-59875` (`GHSA-gvwx-54wh-qm9j`) | **Medium** | `<= 
7.5.16` | `7.5.17` | Uncaught exception DoS via NUL byte in PAX 
`path`/`linkpath` records |
   | `#2465` | `CVE-2026-53655` (`GHSA-vmf3-w455-68vh`) | **Medium** | `<= 
7.5.15` | `7.5.16` | PAX size override applied to intermediary GNU 
long-name/long-link headers |
   
   ## Compatibility & Verification
   
   - **Lockfile integrity**: Updated solely `tar@npm:^7.4.3` -> `7.5.23` via 
Yarn Berry `3.5.0` (`yarn up -R tar`), preserving `yarn.lock` metadata 
(`version: 6`, `cacheKey: 8`) with zero churn to unrelated packages (`1 file 
changed, 10 insertions(+), 11 deletions(-)`).
   - **Unit tests (`jest`)**: Passed all 10 test suites (34/34 tests) in 
`apache-beam-jupyterlab-sidepanel`.
   - **Lint & Typecheck (`eslint` & `tsc --noEmit`)**: Passed cleanly with zero 
errors.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to