Skip to content

fix(deps): bump shell-quote to 1.9.0 (CVE-2026-9277)#455

Merged
anilgangapersaud-circle merged 1 commit into
circlefin:masterfrom
yitianx00:claude/romantic-tu-c4b765
Jun 30, 2026
Merged

fix(deps): bump shell-quote to 1.9.0 (CVE-2026-9277)#455
anilgangapersaud-circle merged 1 commit into
circlefin:masterfrom
yitianx00:claude/romantic-tu-c4b765

Conversation

@yitianx00

Copy link
Copy Markdown
Contributor

Summary

Bumps the transitive shell-quote dependency from 1.8.3 -> 1.9.0 to resolve CVE-2026-9277 (critical: arbitrary code execution via command injection from unescaped input). The patched release is 1.8.4; 1.9.0 is the current resolution within the existing ^1.8.3 range.

Why

The downstream build pipeline runs a Trivy image scan with fail_on_critical: true. The production image SBOM flagged shell-quote CVE-2026-9277 as the only unsuppressed CRITICAL, breaking the build.

shell-quote is pulled in transitively via launch-editor. The existing ^1.8.3 range already permits the fix, so only the resolved lockfile version changes -- no package.json change.

Verification

  • trivy fs --severity CRITICAL on yarn.lock -> 0 vulnerabilities (was 1 in the production image scan).
  • yarn install --frozen-lockfile succeeds (lockfile in sync).
  • Only shell-quote changed; no other dependencies shifted.

🤖 Generated with Claude Code

shell-quote 1.8.3 has a critical command-injection vulnerability
(CVE-2026-9277, arbitrary code execution via unescaped input). The
existing ^1.8.3 range already permits the patched release, so only
the resolved lockfile version changes (1.8.3 -> 1.9.0, >= fixed 1.8.4).

This unblocks the Build Image NG / build_image pipeline, whose Trivy
image scan fails on critical CVEs.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@anilgangapersaud-circle
anilgangapersaud-circle merged commit cf40c5c into circlefin:master Jun 30, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants