MOB-51904: CVE fixes - 2026-07-14#2006
Merged
Merged
Conversation
Auto-fixed by prisma-taurus skill. CVEs fixed: CVE-2026-14324, CVE-2026-14330, CVE-2026-45591
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the build image to remediate newly detected CVEs by upgrading vulnerable OS packages (pipewire) and bumping the bundled .NET SDK used in the Docker image, plus recording the new setuptools-related deferral rationale in the vulnerability history notes.
Changes:
- Extend the
apt-get --only-upgradesecurity block to upgrade pipewire and related packages to patched Ubuntu versions. - Bump .NET SDK download from 8.0.420 → 8.0.422 (URL + SHA512) and update the related
.deps.jsonpatch paths to match the new SDK directory. - Document that the existing
pkg_resourcescoupling now blocks a direct setuptools CVE bump (in addition to the vendored wheel/jaraco.context findings).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| Dockerfile | Upgrades pipewire packages and bumps .NET SDK version/hash; updates dotnet metadata patch paths accordingly. |
| .claude/skills/prisma-taurus/vulnerability_history.md | Adds an explanatory note about the setuptools CVE deferral due to pkg_resources coupling in setup.py. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2006 +/- ##
=======================================
Coverage 88.08% 88.08%
=======================================
Files 73 73
Lines 20935 20935
=======================================
Hits 18439 18439
Misses 2496 2496 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…rst, no diff-size exception)
mykhaliev1
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira: MOB-51904
Fixable in taurus, this run: 3 detected → 3 fixed. (distinct CVEs this repo's own
Dockerfilefixes cleared, confirmed gone in the branch image scan)Verified against the
taurus-branch-builderimage scan (build #576) before opening — integration passed.✅ Fixed (old version gone in branch scan #576)
Fix mechanism
apt-get --only-upgradeblock in thesystem-depsstage (unpinned, so it tracks the security pocket).DOTNET_URL+DOTNET_SHA512), and updated the.deps.jsonsed-patch paths to the new SDK version.Local code review (pre-push)
An independent
/code-reviewpass (high effort) surfaced 2 verification-completeness risks, both consciously deferred to the branch re-scan and both refuted by it:.deps.jsonsed targets might not match 8.0.422's Roslyn versions → refuted: the branch scan shows 0 Roslyn/dotnet rows (no new finding introduced).No code changes were applied from the review (no confirmed defect; speculative edits would have been guesswork).
Fixable but deferred for cause (not in this PR)
setup.pypkg_resourcescoupling: clearing them requires setuptools ≥ 82/83 which removespkg_resources, breaking the no-build-isolation wheel build (setup.py:16stillimport pkg_resources). The real unblock is a separate PR refactoringsetup.pyontopackaging.requirements— it would clear all three at once.diff ^7; the fix crosses a major for a single LOW.Not actionable in this repo (count only)
pip 24.0 (distro apt can't reach 26.1.2) + monitor-only JMeter/Gatling bundled jars, Ubuntu ESM, k6 binary internals, no-released-patch, and scanner-appeasement findings. Criticals this run: all 4 are monitor-only JMeter/Gatling bundled jars (Apache Tika) — none fixable here.
Raw scan (reconciliation only): baseline #178 278 → branch #576 259 [crit 4→4, high 44→43, medium 169→165, low 48→47]. Distinct-CVE counts differ from per-occurrence totals — context, not a checksum.
🤖 Generated with Claude Code