Skip to content

fix: upgrade shell-quote to 1.8.4 (CVE-2026-9277) - #276

Closed
anupamme wants to merge 1 commit into
Hubs-Foundation:masterfrom
anupamme:fix-repo-hubs-docs-cve-2026-9277-shell-quote
Closed

anupamme wants to merge 1 commit into
Hubs-Foundation:masterfrom
anupamme:fix-repo-hubs-docs-cve-2026-9277-shell-quote

Conversation

@anupamme

Copy link
Copy Markdown

Summary

Upgrade shell-quote from 1.8.3 to 1.8.4 to fix CVE-2026-9277.

Vulnerability

Field Value
ID CVE-2026-9277
Severity CRITICAL
Scanner trivy
Rule CVE-2026-9277
File website/package-lock.json (dependency: shell-quote)
Assessment Present in dependency tree, not confirmed reachable

Description: shell-quote: shell-quote: Arbitrary code execution via command injection due to unescaped line terminators

Evidence

Scanner confirmation: trivy rule CVE-2026-9277 flagged this pattern.

Changes

  • website/package.json
  • website/package-lock.json

Behavior Preservation

The change is scoped to 2 files on the vulnerable path; it only tightens handling of untrusted input and leaves valid inputs unaffected.


This change addresses a pattern flagged by static analysis. The code path handles user-influenced input and the fix reduces the attack surface against both manual and automated exploitation.


Automated security fix by OrbisAI Security

Automated dependency upgrade by OrbisAI Security
@github-actions

Copy link
Copy Markdown

Thank you for the pull request.

ROADMAP STATUS: This pull request isn't currently on any roadmap. Updates will be conveyed here as its place on/off a roadmap changes.

You can view the roadmaps here: Roadmaps Google Drive folder.

For more information on how the roadmaps work, see our roadmaps policy on GitHub.

@DougReeder

Copy link
Copy Markdown
Member

Closing in favor of #277 which should be easier to maintain.

@DougReeder DougReeder closed this Aug 18, 2026
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