Repository navigation
[Security Maintenance Proposal] Refresh three Vite lockfiles for GHSA-p4f5-76q4-ffq7 #2424
Closed
KatkamKoushik
started this conversation in
Ideas
Replies: 1 comment 1 reply
|
Thanks for reporting all three lockfiles and documenting the dev-server exposure condition. I confirmed the upstream advisory and opened maintainer PR #2434. It updates the web catalog to Vite 8.3.7, the Loki Mode frontend to 8.1.7, and Stageshow to 6.4.6. The local maintainer preflight, web tests and production build, both example builds, and Stageshow’s launcher tests passed. npm audit returned zero findings before and after the refresh, so the advisory’s version ranges and the verified lockfile resolutions are the evidence for this specific fix. The PR is open for CI and review. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
The publicly disclosed Vite security advisory GHSA-p4f5-76q4-ffq7 describes a critical development-server vulnerability that may permit arbitrary code execution when a vulnerable Vite server is explicitly exposed to the network.
I inspected three committed dependency lockfiles in
sickn33/agentic-awesome-skills, using upstream commit444f05edf05566b0880ad34e8eba6e9034905483as the baseline.Affected lockfiles
apps/web-app/package-lock.jsonskills/loki-mode/examples/todo-app-generated/frontend/package-lock.jsonskills/stageshow/package-lock.jsonEach package manifest already has a semver range that permits a patched version. The lockfiles currently retain vulnerable resolutions.
Exposure and limitations
The three inspected Vite configurations use default localhost binding or explicitly bind to
127.0.0.1.This reduces exposure during normal local development. However, users may expose the development server through command-line overrides, port forwarding, or other environment configurations.
This report identifies vulnerable dependency versions; it does not demonstrate an exploitable deployment.
Proposed maintainer action
Please consider refreshing the three canonical lockfiles to patched Vite releases, preserving their existing major-version compatibility.
It would also be useful to verify lockfile consistency, dependency audits, focused application tests, and builds after the upgrades.
The source repository contains generated plugin mirrors; those should be handled through the repository's normal maintainer synchronization process.
Contributor-policy limitation
The repository's
tools/lib/workflow-contract.jsdoes not admit these lockfile paths through the standard external-fork contributor workflow.I am raising this as a maintenance proposal rather than opening a PR that would fail intake.
Validation status
The affected versions and the applicable upstream advisory have been verified.
Initial test/build attempts against the unchanged upstream baseline encountered a Vitest timeout and missing local setup prerequisites. These do not establish whether the patched versions pass. No post-upgrade test success is claimed.
Thank you for maintaining the project's dependency and security review processes.
All reactions