MOB-51315: CVE fixes - 2026-06-25#1999
Merged
Merged
Conversation
Auto-fixed by prisma-taurus skill. CVEs fixed: CVE-2026-8376, CVE-2026-42496 (perl), CVE-2026-6653 (libxml2) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Verify npm's bundled dep version (undici/glob/cross-spawn) before assuming a global npm bump fixes a CVE; undici stayed at 6.26.0 even in npm 11.17.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1999 +/- ##
=======================================
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:
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR applies automated CVE remediation to the blazemeter/taurus:unstable image by upgrading specific Ubuntu packages in the Docker build, and it updates the internal vulnerability remediation playbook to avoid assuming an npm global upgrade fixes bundled transitive deps.
Changes:
- Upgrade
perlandlibxml2viaapt-get install --only-upgradein the Dockerfile’s system-deps stage to pick up patched Ubuntu builds. - Add/clarify guidance in
vulnerability_history.mdabout verifying npm’s bundled dependency versions (e.g., undici) before treating an npm bump as a fix.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
Dockerfile |
Adds perl and libxml2 to the existing OS-package --only-upgrade CVE remediation step. |
.claude/skills/prisma-taurus/vulnerability_history.md |
Documents a verification step for npm-bundled dependency versions to prevent ineffective “fixes”. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
henrychv
approved these changes
Jun 25, 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-51315
Summary
Automated CVE remediation for
blazemeter/taurus:unstable, applied by theprisma-taurusskill and verified in the built image before opening this PR viataurus-branch-builder#570 (build + integration + Prisma scan).Fixes (apt
--only-upgrade, non-ESM standard updates — Dockerfile system-deps stage)All three are verified absent (0 occurrences) in the branch image scan.
Branch-image scan comparison
Verified against the
taurus-branch-builderimage scan (build #570) before opening — integration passed and vulnerabilities dropped:Critical stays at 4 — all four are Apache Tika jars bundled in JMeter (out of scope; not remediated by jar repin or JMeter/Gatling version bump).
Also in this PR
vulnerability_history.md: recorded that npm-bundled deps (undici/glob/cross-spawn) must be version-checked at the npm/cli tag before assuming a global npm bump fixes them — undici stayed at 6.26.0 even in npm 11.17.0.NOT fixed — require manual intervention or are out of scope
_vendor(wheel, jaraco.context) — already pin latest-compatible setuptools 79.0.1.file-type(breaking major jump), Mochadiff(pins ^7, no in-range fix), system distro pip, .NET asp.net-core 8.0.26 (CVSS 0, high SDK-bump churn).🤖 Generated with Claude Code