[rhoai-2.25] fix(cve): bump pyasn1 to >=0.6.4 for CVE-2026-59885 - #2625
[rhoai-2.25] fix(cve): bump pyasn1 to >=0.6.4 for CVE-2026-59885#2625BabbarPB08 wants to merge 0 commit into
Conversation
|
@BabbarPB08 — This PR is from a fork. Recommended: Push your branch to the main repo for full CI: Then open a new PR from that branch. No push access? A maintainer will cherry-pick and test your changes. See CONTRIBUTING.md for details. |
📝 WalkthroughWalkthroughChangespyasn1 dependency update
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## rhoai-2.25 #2625 +/- ##
============================================
Coverage ? 0
============================================
Files ? 0
Lines ? 0
Branches ? 0
============================================
Hits ? 0
Misses ? 0
Partials ? 0 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
jupyter/pytorch+llmcompressor/ubi9-python-3.12/pylock.toml (1)
1-1: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick winUpgrade or regenerate the flagged
clicklock entry.
jupyter/pytorch+llmcompressor/ubi9-python-3.12/pylock.tomlstill pinsclick==8.1.8, which is below the fixed version for PYSEC-2026-2132. Regenerate/lock this file to a fixedclickversion so the OSV scanner finding is resolved alongside the CVE PR.🤖 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 `@jupyter/pytorch`+llmcompressor/ubi9-python-3.12/pylock.toml at line 1, Regenerate the autogenerated pylock.toml using uv so its click lock entry is upgraded from 8.1.8 to a version fixed for PYSEC-2026-2132, while preserving the rest of the dependency lockfile.Source: Linters/SAST tools
🤖 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.
Outside diff comments:
In `@jupyter/pytorch`+llmcompressor/ubi9-python-3.12/pylock.toml:
- Line 1: Regenerate the autogenerated pylock.toml using uv so its click lock
entry is upgraded from 8.1.8 to a version fixed for PYSEC-2026-2132, while
preserving the rest of the dependency lockfile.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 6c0ffe36-7987-45a3-8b4c-6b17a2c53d15
📒 Files selected for processing (17)
codeserver/ubi9-python-3.12/pylock.tomldependencies/cve-constraints.txtjupyter/datascience/ubi9-python-3.12/pylock.tomljupyter/minimal/ubi9-python-3.12/pylock.tomljupyter/pytorch+llmcompressor/ubi9-python-3.12/pylock.tomljupyter/pytorch/ubi9-python-3.12/pylock.tomljupyter/rocm/pytorch/ubi9-python-3.12/pylock.tomljupyter/rocm/tensorflow/ubi9-python-3.12/pylock.tomljupyter/tensorflow/ubi9-python-3.12/pylock.tomljupyter/trustyai/ubi9-python-3.12/pylock.tomlruntimes/datascience/ubi9-python-3.12/pylock.tomlruntimes/minimal/ubi9-python-3.12/pylock.tomlruntimes/pytorch+llmcompressor/ubi9-python-3.12/pylock.tomlruntimes/pytorch/ubi9-python-3.12/pylock.tomlruntimes/rocm-pytorch/ubi9-python-3.12/pylock.tomlruntimes/rocm-tensorflow/ubi9-python-3.12/pylock.tomlruntimes/tensorflow/ubi9-python-3.12/pylock.toml
CI analysis @
|
| Job | Root cause |
|---|---|
| rocm-jupyter-pytorch / rocm-runtime-pytorch | ENOSPC writing /var/tmp/container_images_storage* (known #2554) |
| jupyter-minimal ppc64le / s390x | qemu OpenShift wait / CrashLoop (known tip flake) |
| runtime-datascience s390x | pyzmq compile under qemu (known tip flake) |
| jupyter-datascience ppc64le | numpy sdist No BLAS — tip now has #2534 openblas-devel; rebase should clear this |
| codeserver amd64 / arm64 | image built OK; post-step missing scripts/get_playwright_version.py (tip/workflow mismatch — rebase should pick up tip script) |
Ignore — PR-event run 30310541194: ~25✗ early
Fork without repo secrets (SUBSCRIPTION_*, AIPCC_QUAY_BOT_*, GIT_CRYPT_KEY). Codeserver×2 succeeded (no subscription). Expected for fork PRs — use AIPCC pull_request_target lane / same-repo branch for real build signal.
Recommended next
- Rebase onto tip
rhoai-2.25(clears dirty + picks up [rhoai-2.25] fix(ppc64le): openblas-devel for ONNX numpy builds #2534 / [rhoai-2.25] RHAIENG-6036: fix trustyai k8s papermill probe timing #2487 / PDF+check-payload fixes). - Re-check AIPCC matrix; treat remaining pyzmq / ENOSPC / qemu as tip flakes unless new.
d7fe079 to
185270c
Compare
|
Rebased onto current New HEAD: Conflict resolution:
PR is MERGEABLE again (was CONFLICTING). CI should re-run on the new SHA. |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
jupyter/trustyai/ubi9-python-3.12/pylock.toml (1)
1707-1744: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick winRemove the unrelated Pillow lockfile update.
This PR targets pyasn1 CVE-2026-59885, but this stanza also changes Pillow to 12.3.0 and refreshes its wheel set. Revert these Pillow changes or split them into a separately reviewed update so this image does not receive an unreviewed runtime dependency change.
Based on learnings, non-ROCm per-image lockfiles should not be regenerated in this CVE-fix flow; ROCm TensorFlow images are the documented exception.
🤖 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 `@jupyter/trustyai/ubi9-python-3.12/pylock.toml` around lines 1707 - 1744, Remove the unrelated Pillow 12.3.0 lockfile stanza and restore the prior Pillow dependency entries, leaving only the pyasn1 CVE update in this change. Do not regenerate non-ROCm per-image lockfiles for this CVE-fix flow; preserve lockfile changes only where required for the documented ROCm TensorFlow exception.Source: Learnings
🤖 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.
Outside diff comments:
In `@jupyter/trustyai/ubi9-python-3.12/pylock.toml`:
- Around line 1707-1744: Remove the unrelated Pillow 12.3.0 lockfile stanza and
restore the prior Pillow dependency entries, leaving only the pyasn1 CVE update
in this change. Do not regenerate non-ROCm per-image lockfiles for this CVE-fix
flow; preserve lockfile changes only where required for the documented ROCm
TensorFlow exception.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: fc5a5c84-c391-45f6-aeb9-4eab18535e3e
📒 Files selected for processing (13)
dependencies/cve-constraints.txtjupyter/datascience/ubi9-python-3.12/pylock.tomljupyter/pytorch+llmcompressor/ubi9-python-3.12/pylock.tomljupyter/pytorch/ubi9-python-3.12/pylock.tomljupyter/rocm/pytorch/ubi9-python-3.12/pylock.tomljupyter/rocm/tensorflow/ubi9-python-3.12/pylock.tomljupyter/tensorflow/ubi9-python-3.12/pylock.tomljupyter/trustyai/ubi9-python-3.12/pylock.tomlruntimes/datascience/ubi9-python-3.12/pylock.tomlruntimes/pytorch/ubi9-python-3.12/pylock.tomlruntimes/rocm-pytorch/ubi9-python-3.12/pylock.tomlruntimes/rocm-tensorflow/ubi9-python-3.12/pylock.tomlruntimes/tensorflow/ubi9-python-3.12/pylock.toml
🚧 Files skipped from review as they are similar to previous changes (1)
- dependencies/cve-constraints.txt
Same-repo branch for full CIFork PR CI is expected to fail on RHEL/AIPCC (and similar) jobs: workflows from forks cannot access the required repo secrets. See CONTRIBUTING — Contributing from branches vs forks. For RHDS, the recommended path is a PR from a branch pushed to
Leaving this fork PR open for reference; no need to close it unless you want to. Tracker: RHAIENG-6370. |
|
/build-konflux |
185270c to
6ae9aaa
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jiridanek The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Thanks @BabbarPB08 — rebased this branch onto current
After rebase, the pyasn1 commit is fully superseded by the merged CVE batch in #2634 ( Closing as superseded by #2634 — your original change is landed; no further action needed on this PR. |
Summary
pyasn1from 0.6.3 to >=0.6.4 to fix CVE-2026-59885 (DoS via crafted ASN.1 OBJECT IDENTIFIER / RELATIVE-OID)dependencies/cve-constraints.txtand regenerates affectedpylock.tomlfilesPrefer same-repo PR for merge / full CI: #2633
Build Notebooks (push): https://github.com/red-hat-data-services/notebooks/actions/runs/30370187977
Fork PR CI cannot use
SUBSCRIPTION_*/AIPCC_QUAY_BOT_*/GIT_CRYPT_KEYsecrets — use #2633 for validation.Test plan
pylock.tomlfiles pinpyasn1to 0.6.4rhoai-2.25